> Does the file system pad lines with spaces?
Yes it does! It seems that the file is very similar to the old-style IBM
punch cards, where everything had 80 columns, and anything that wasn't
filled in was a space. The file is filled out to column 81 with spaces,
and the \ is in column 66. Shouldn't lclint just ignore the whitespace
following the trailing \?
Anthony Giorgio
DBX Developer
Phone: (845) 435-9115
Tie Line: 295-9115
Email: agiorgio AT us.ibm.com
Derek M Jones <[EMAIL PROTECTED]>
09/28/2001 11:33 AM
To: Anthony Giorgio <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED]
Subject: Re: LCLint 3.0.0.17 parse problem
Anthony,
>I'm using LCLint 3.0.0.17 on an IBM zSeries mainframe, and I'm having
Does the file system pad lines with spaces?
>problems getting it to parse the code for the project I'm on. Whenever
it
>tries to parse one of the systerm header files, it gags on the
>preprocessor step. Many of the header files have a construct similar to
>the one below:
>
> #if (lots_of_stuff) \
> && (other_stuff)
> #define some_flag
> #endif
>
>
>Whenever I run lclint on a file that includes a header with the above
>construct, it dies with the following errror:
>
>/usr/include/features.h:203:67: Invalid character in #if: \
>
>Is it valid to allow #if directives to span lines with the use of '\' ,
This error message is very specific. Perhaps it is a bug in LCLint.
The code is certainly conforming.
>and if so, how can I convince lclint that it's okay? If it's not valid,
>then how can I have lclint ignore the problem? I can't change the system
>header files to make them more compliant, even though it might be a good
>idea :)
They are already compliant. Nothing to change.
derek
--
Derek M Jones tel: +44 (0) 1252
520 667
Knowledge Software Ltd mailto:[EMAIL PROTECTED]
Applications Standards Conformance Testing http://www.knosof.co.uk
