You can do a lot by making a custom LCD file for Splint but, AFAIK,
supporting the non-standard binary literal extension '0b000" and binary data
types, is not possible without modifying the source code.

I avoid non-standard C extensions whenever possible because of the
non-portability so, this hasn't been an issue for me.

Paul

> -----Original Message-----
> From: piclist-bounces@mit.edu On Behalf Of Gerhard Fiedler
> Sent: Thursday, December 16, 2004 3:37 PM
>
> Thanks to Paul I gave splint a try. After setting up the basics (splint
> configuration files, compiler include file path, excluding the compiler
> include files from the check etc.) and having it basically working, I ran
> into a problem.
>
> I use HiTech PICC/PICC-18, and it supports the "bit" type and the "0b01"
> binary constant. Both resulted in a "parse error" with splint.
>
> I could solve the "bit" type problem by #defining it to "int" for the
> check, but I didn't find a suitable way to make splint work with
> the "0b01"
> binary constants.
>
> Since at least Paul seems to be using a similar tool for some time, maybe
> there's a solution -- other than not using 0b01 type constants. I asked on
> the HiTech forum, and the responses were to use a custom pre-preprocessor
> to rewrite the binary constants, or to not use them at all.
>
> This is probably similar with most small embedded processor compilers --
> they usually will have some non-standard extensions that need to be made
> known to the lint type tool of choice.
>
>
> > For those who want a tool with commercial support,
> > I've seen PC-lint from Gimpel Software highly recommended
> numerous times by
> > the experts at ESP http://www.gimpel.com.
>
> PC-lint apparently has a configuration option to enable support for binary
> constants. But I don't really want to spend the money...
>
> Thanks,
> Gerhard

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