[splint-discuss] Option to allow gcc mixed code/declarations
Michael Wojcik
Michael.Wojcik at MicroFocus.com
Thu Jul 6 10:14:45 EDT 2006
> From: splint-discuss-bounces at cs.virginia.edu
> [mailto:splint-discuss-bounces at cs.virginia.edu] On Behalf Of
> Auguste Venkiah
> Sent: Thursday, 06 July, 2006 08:43
>
> Le jeudi 06 juillet 2006 à 08:59 +0100, John Matthews a écrit :
> > Thanks Auguste- I appreciate that the code isn't C90. But then neither
> > are the other gcc extensions that +gnuextensions tells splint to
> > ignore; why not this as well?
>
> I guess that the +gnuextensions should have been a solution to this
> problem. However, I remember having seen this topic on the
> mailing list before.
> Clearly, this seems to be an issue to many people, but maintainers seem
> to have very little time.
Splint isn't actively maintained, according to discussions on the list at the end of last year. David Evans asked for volunteers (in a message dated 2005-12-18) but I don't believe anyone stepped up.
> Noboby actually seems to be in the position to
> update the parser to support ISO C99.
Since C99-conformant implementations are rare and have little market share, C99 is hardly the best near-term goal for Splint updates. (GCC is not C99-conformant.) Adding support for declarations anywhere in a block, as part of +gnuextensions and/or another option, would make more sense.
(It wouldn't be one of *my* priorities, because I dislike that "extension" and would much rather see various bugs in processing conforming C code fixed, but hey - it's open source, so people can fix whatever they like.)
--
Michael Wojcik
Principal Software Systems Developer, Micro Focus
More information about the splint-discuss
mailing list