Simon Hosie wrote:
Meek, Richard:
I've also received a few suggestions from your fellow countryman
Simon Hosie (thanks Simon!)
What? Oh! That's where that went. Stupid Outlook. Some other
group sets 'reply-to', and I get confused.
Most other lists do. [EMAIL PROTECTED] (gnu pascal
Simon Hosie wrote:
CBFalconer:
Please don't toppost.
Just so I don't do it by accident; what does that mean?
It means posting ahead of the material you are quoting, rather
than interspersed or afterwards.
--
Chuck F ([EMAIL PROTECTED]) ([EMAIL PROTECTED])
Available for consulting
Austin Hastings wrote:
I'm considering using splint for a large-scale open-source development
effort that is currently in very early development, although a fair
chunk of code has been written.
This means that there's going to be a lot of code coming in, and most
of it, initially, won't
David Evans wrote:
With splint versions before 3.1, you still need a typedef for
bool (even if you use the -booltype bool flag) since bool is
not a builtin type. With Splint 3.1 and later, bool is builtin.
I have 3.0.1.6 here. I have seen no announcements on this list of
any later versions.
David Hawkins wrote:
Please don't top-post.
Enlighten me? What do you mean by 'top-post'?
And sorry for doing it :)
Top posting is posting before the quoted material to which you are
replying, which you did before, but not this time. It is
encouraged by brain-dead software such as
Gaurav Mathur wrote:
Suppose I have the following code fragment
void func (int x, int y)
{
if (x0)
y = 1;
else
y = 0;
}
How do I capture the semantics that y is either
0 or 1 after this function returns. Could I use
ensures
FND-AD YAO Roy wrote:
Part 1.1Type: Plain Text (text/plain)
Encoding: quoted-printable
You might start by avoiding html or attachments in e-mail, which
is also a security risk. After that it is possible your problems
have to do with the global space shortage, and your
Jens Krinke wrote:
the 2nd edition of the german book open source programming tools
has a new chapter about splint. The book is now being translated
and for that reason we are looking for a native speaker who would
be interested to read (and comment) the splint chapter before
publication.
Bertrand ANSEAUME wrote:
I have a problem to detect incomplete deallocation of a structure
that includes two buffers buf1 and buf2 (see code sample below).
If I don't release buf1 and buf2, Splint correctly detects the two
memory leaks. But if I release buf1 only, Splint does not detect
David Hawkins wrote:
Given the following command line arguments
(RedHat Linux 9.0 machine, Linux 2.4.20-8 kernel):
splint +posixlib buffer_queue.c -I../boolean
where I have used a pthread_mutex_t inside the
buffer queue implementation to protect it.
I'm getting the following parse error
Saravana.Rathinam wrote:
David Hawkins wrote:
Given the following command line arguments
(RedHat Linux 9.0 machine, Linux 2.4.20-8 kernel):
splint +posixlib buffer_queue.c -I../boolean
where I have used a pthread_mutex_t inside the
buffer queue implementation to protect it.
I'm getting
Richard A. O'Keefe wrote:
[EMAIL PROTECTED] wrote:
Line in Source Code:
(void *)pIIC = (void *)strPS.cBuf;
Splint detects a parse error with (void *)
more precisely, with the first one. Sinister casts have never
*ever* been legal C, and they are quite unnecessary.
Sekuri, Yaminikrishna (GE Consumer Industrial) wrote:
I am using SPLINT to check my code for ANSI compliance.
I get the Parser error with respect to pthreads.
My source code file source.c includes a file xyz.h which in turn
has pthread_t structure and a function which return this structure.
Ralf Wildenhues wrote:
* Mike Solem wrote on Tue, Aug 24, 2004 at 05:28:34PM CEST:
I see what you're doing, but can't get it to work for what I want.
I'm assuming ~1 is some kind of name completion symbol. It seems
to only work when there are 6 preceding characters. Example:
David Evans wrote:
Yes, splint's analysis merges the null state after the if, but
loses the information from the predicate test (to know that
buf-data was already NULL), so you get the spurious warnings.
If you change the code to,
if (buf-data != NULL) {
free(buf-data);
}
[EMAIL PROTECTED] wrote:
Part 1.1.1Type: Plain Text (text/plain)
Part 1.2Type: Plain Text (text/plain)
Encoding: 7bit
Disposed of out of hand as containing potentially dangerous html
and attachments. e-mail is a text only medium.
--
I support the Red Sox and any
16 matches
Mail list logo
