LCLint Trigraph problem

NT__ , but I think this may be a larger problem than I first realized. Thanks for all the help so far. Anthony Giorgio DBX Developer Phone: (845) 435-9115 Tie Line: 295-9115 Email: agiorgio AT us.ibm.com "Thou shalt not follow the Null Pointer, for at its end Chaos and Madness lie."

Re: LCLint 3.0.0.17 parse problem

e backslash char (0xE0) and the newline. On another note, please excuse my ignorance of optimizing compilers and the like. I'm just starting out, and learning just how much I need to learn. Anthony Giorgio DBX Developer Phone: (845) 435-9115 Tie Line: 295-9115 Email: agiorgio AT us.i

Re: LCLint 3.0.0.17 parse problem

olumn 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

LCLint 3.0.0.17 assertion bug

d be done is have a #if EBCDIC construction which removes any uneeded code here at compile time. There's certainly no need to check the charset every time the function is called! Anthony Giorgio DBX Developer Phone: (845) 435-9115 Tie Line: 295-9115 Email: agiorgio AT us.ibm.com

LCLint 3.0.0.17 parse problem

s it valid to allow #if directives to span lines with the use of '\' , 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 i