I was thinking of having a /*@range ...@*/ clause for function parameters
and return values, like:
void handle_ferror(int input /*@range 0-UCHAR_MAX, EOF@*/) { }
socket.c:12:15: Parse Error: Inconsistent function declaration: fd_set :
int. (For help on parse errors, see splint -help parseerrors.)
the only thing ever declared fd_set is only declared once and isn't even
a function! Help!
On many programs, splint gives me a preprocessing error, but doesn't tell
me what it is.
On Mon, 13 May 2002, eschner wrote:
>
> Hi,
>
> a couple of days ago I gave splint a try (it looked rather attractive to
> me).
>
> However, I did not get too far due to parse errors occuring on multi-line
> #define's. E.g.
>
> blog.h: 153:6: Parse Error. (For help ...
>
> Here's the corresp
On Tue, 13 Aug 2002, Massimiliano Cialdi wrote:
> I need to search for uninitialized variables in a not-instrumented
> source code (w/o annotations). No problem with local (automatic)
> variables but I don't know how to analize global variables.
>
> for example:
>
>
