> -----Original Message-----
> From: piclist-bounces@mit.edu On Behalf Of William "Chops" Westfield
> Sent: Sunday, February 07, 2010 6:31 PM
>
> On Feb 7, 2010, at 3:13 PM, Jason Hsu wrote:
>
> > I'm finding that splint has difficulty with
> > the "__CONFIG" line even though the code compiles (and despite the
> > fact that I moved a copy of the *.h files to the directory where
> > splint expects to see such files) and refuses to go any further.


Adding the #pragma directive should stop Splint from complaining, e.g.
"#pragma __CONFIG ...".

If that doesn't work then, as BillW pointed out, an #ifndef S_SPLINT_S
construct will take care of it.

Paul Hutch

>
> It's relatively common for a program (especially an embedded program)
> to contain constructs that assorted "code analysis" tools don't like,
> and it's likewise common to therefore see constructs like:
> #ifndef LINT
>    __CONFIG ...
> #endif
> (__CONFIG doesn't have any other effect on C code generation, right?
> It gets a bit more complicated when you have something NECESSARY for
> the rest of the program to compile, that lint STILL doesn't like.)
>
> BillW

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist