<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2912" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff><FONT face=Arial size=2>
<DIV>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?</DIV>
<DIV> </DIV>
<DIV>Yes, I can modify the offending code, but there's quite a lot of it
:-(</DIV>
<DIV> </DIV>
<DIV>John</DIV>
<DIV> </DIV>
<DIV>> The only way I got arround this is :<BR>><BR>> #ifndef
S_SPLINT_S<BR>> /* Code to ignore be ignored by splint */<BR>>
#endif<BR>><BR>> Splint conforms to ISO C90 which does not allow
intermixed code and<BR>> declarations. All declarations have to be at the top
of a block. <BR>><BR>> That is to say : there is no way of 'telling'
splint that your piece of<BR>> code is OK because is not ISO C90; however,
you can tell splint to<BR>> ignore the corresponding line in order to avoid
parse errors.<BR>><BR>> Le mercredi 05 juillet 2006 à 14:25 +0100, John
Matthews a écrit :<BR>> ><I> Hi- I'm trying to use splint to check some
existing code that has<BR></I>> ><I> variable declarations within code ie.
not just at the top of blocks, as<BR></I>> ><I> allowed by gcc. Is there a
way of persuading splint that this is ok,<BR></I>> ><I> instead of
stopping with a parse error? BTW +gnuextensions doesn't<BR></I>> ><I>
help.<BR></I>> ><I> TIA<BR></I>> ><I>
John</I></DIV></FONT><BR><B>This email and any files transmitted with it are confidential and intended solely for the use of the individuals to whom they are addressed. If you have received this email in error please notify the sender and delete the message from your system immediately.</B><BR>
</BODY></HTML>