lclint-interest message 173

From Michael.Diack@ukos.varian.com Sat Oct  4 13:46:30 1997
From: Michael.Diack@ukos.varian.com (Michael Diack)
Return-Receipt-To: Michael.Diack@ukos.varian.com (Michael Diack)
To: lclint-interest@larch.lcs.mit.edu (lclint-interest),
        miho@osn.de (Michael Hohner)
X-Conversion-Id: 
X-Mailer: cc:Mail via PostalUnion/SMTP for Windows NT
Mime-Version: 1.0
Date: Sat, 04 Oct 1997 08:38:56 +0100
Subject: Re: Introduction
Content-Type: text/plain; charset="US-ASCII"

 
I agree with this - this is a source of annoyance and means the use of grep
etc.
to sort the real messages from these. Putting an option in the next version to 
cure this would be really good.

Mike

______________________________ Reply Separator
_________________________________
Subject: Introduction
Author:  Michael Hohner  at Internet-Mail
Date:    04/10/97 07:59


 Hello !
 
 I'm new to this mailing list and like to introduce myself. I'm working for 
 a german company making real-time system software, and we're using LCLint 
 to double check our code. Compilers for embedded systems are usually quite 
 weak, even at the highest warning level, and they don't catch a lot of 
 problems that other compilers do spot.
 
 We're using the Linux version of LCLint. The compilers, however, run on DOS 
 or Windows, so the source files on the server naturally contain CRLF line 
 enders. LCLint complains about the CR's. It would be nice if LCLint had an 
 option to ignore CR's (or even better, an option to specify which line 
 enders (LF, CRLF or CR) are used). This would save us making copies of the 
 source and header files for conversion.
 
 
 
 Servus, Michael!
 
 Internet:   miho@osn.de
 Fidonet:    2:2490/2520.17



Previous Message Next Message Archive Summary LCLint Home Page David Evans
University of Virginia, Computer Science
evans@cs.virginia.edu