From beroset at mindspring.com  Tue Jan  1 08:30:08 2008
From: beroset at mindspring.com (Ed Beroset)
Date: Tue, 01 Jan 2008 11:30:08 -0500
Subject: [splint-discuss] recognize typedef'd void?
In-Reply-To: <c4e763ac0712311257r1580d7f7g527595776e3f2d0a@mail.gmail.com>
References: <c4e763ac0712311257r1580d7f7g527595776e3f2d0a@mail.gmail.com>
Message-ID: <477A6A90.4020508@mindspring.com>

Aaron Davies wrote:
> is it just me, or should this produce no warnings?
> 
> typedef void V;
> static V foo(){return;}
> int main(/*@unused@*/int argc,/*@unused@*/char**argv){foo();return 0;}

I can see why it would produce a warning.  It's because it is trying to 
support the notion of abstract types in support of information hiding. 
It doesn't seem to notice that V is void -- I'm not sure I'd classify 
this as a bug, though.

Ed

From ptp at lysator.liu.se  Wed Jan  2 07:54:08 2008
From: ptp at lysator.liu.se (Tommy Pettersson)
Date: Wed, 2 Jan 2008 16:54:08 +0100
Subject: [splint-discuss] string concatenation patch
In-Reply-To: <47790224.1020108@mindspring.com>
References: <47790224.1020108@mindspring.com>
Message-ID: <20080102155408.GA4078@static-81.216.50.98.addr.tdcsong.se>

On Mon, Dec 31, 2007 at 09:52:20AM -0500, Ed Beroset wrote:
> +	case '\\':
> +	  *ss++ = *ts++;
> +	  escape = TRUE;
> +	  /*@switchbreak@*/ break;

I think this code will mess up an escaped backslash, e.g.,

  "foo \\" FOOBAR " bar"


Anyway, it's nice to see splint improving.



-- 
Tommy Pettersson <ptp at lysator.liu.se>

From beroset at mindspring.com  Wed Jan  2 08:52:26 2008
From: beroset at mindspring.com (Ed Beroset)
Date: Wed, 02 Jan 2008 11:52:26 -0500
Subject: [splint-discuss] string concatenation patch
In-Reply-To: <20080102155408.GA4078@static-81.216.50.98.addr.tdcsong.se>
References: <47790224.1020108@mindspring.com>
	<20080102155408.GA4078@static-81.216.50.98.addr.tdcsong.se>
Message-ID: <477BC14A.70600@mindspring.com>

Tommy Pettersson wrote:
> On Mon, Dec 31, 2007 at 09:52:20AM -0500, Ed Beroset wrote:
>> +	case '\\':
>> +	  *ss++ = *ts++;
>> +	  escape = TRUE;
>> +	  /*@switchbreak@*/ break;
> 
> I think this code will mess up an escaped backslash, e.g.,
> 
>   "foo \\" FOOBAR " bar"

You're right.  Thanks for the bug report.  I'll fix that.

> Anyway, it's nice to see splint improving.

When I fix this, I hope it really will be an improvement.

Ed

From maratsafinwang at gmail.com  Fri Jan 11 09:50:02 2008
From: maratsafinwang at gmail.com (Wang Safin)
Date: Sat, 12 Jan 2008 01:50:02 +0800
Subject: [splint-discuss] About Source Code of Splint
Message-ID: <7d34b6c00801110950k480d8338v65cf065fe7af52d3@mail.gmail.com>

Hi everyone,
I am a newcomer, and I'm trying to read the source code of Spint-3.11. I
have not enough informations about the structure or anything else about the
source, so it's a difficult job for me.
Does anyone have some papers or something else about the source code?
Thank you for help!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.cs.virginia.edu/pipermail/splint-discuss/attachments/20080112/35a29b31/attachment.html 

From noreply at mail.goodreads.com  Thu Jan 17 21:52:59 2008
From: noreply at mail.goodreads.com (Jack Sparrow)
Date: Thu, 17 Jan 2008 21:52:59 -0800
Subject: [splint-discuss] Let's compare books
Message-ID: <47903ebb46e39_1779..fdbf2c3841564603f2@dv3.goodreads.com.tmail>


splint-discuss,

Please add me as a friend on Goodreads:

http://www.goodreads.com/friend/i?e=splint-discuss at mail.cs.virginia.edu&i=LTM2MDY0NTAxODM6MzE3
&n=splint-discuss&utm_medium=email&utm_source=general

- Jack (virtualspy3 at gmail.com)




To opt-out of future invites to Goodreads please follow this link: http://www.goodreads.com/user/block_email?inviter_id=647471&utm_medium=email&utm_source=general	



This email was sent by request to splint-discuss at mail.cs.virginia.edu.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.cs.virginia.edu/pipermail/splint-discuss/attachments/20080117/95344bf4/attachment-0001.html 

From noreply at mail.goodreads.com  Thu Jan 17 21:52:59 2008
From: noreply at mail.goodreads.com (Jack Sparrow)
Date: Thu, 17 Jan 2008 21:52:59 -0800
Subject: [splint-discuss] Let's compare books
Message-ID: <47903ebb9498e_1779..fdbf2c384156462391@dv3.goodreads.com.tmail>


Discussions,

Please add me as a friend on Goodreads:

http://www.goodreads.com/friend/i?e=splint-discuss at cs.virginia.edu&i=LTM2MDY0NTAxODM6MzE3
&n=Discussions&utm_medium=email&utm_source=general

- Jack (virtualspy3 at gmail.com)




To opt-out of future invites to Goodreads please follow this link: http://www.goodreads.com/user/block_email?inviter_id=647471&utm_medium=email&utm_source=general	



This email was sent by request to splint-discuss at cs.virginia.edu.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.cs.virginia.edu/pipermail/splint-discuss/attachments/20080117/cd69cf31/attachment.html 

From Sebastian.Matuschka at gcd-solutions.de  Mon Jan 28 23:18:04 2008
From: Sebastian.Matuschka at gcd-solutions.de (Matuschka, Sebastian)
Date: Tue, 29 Jan 2008 08:18:04 +0100
Subject: [splint-discuss] Skip code parts
Message-ID: <49ED01FC03EE524BB7BB258E8F93BFF319A776@bfl-exchange-1.BFL.local>

Hi,

i want to skip code parts that are between "#pragma asm" and "#pragma
endasm" because Splint ends with a parse error when it parses this code.
I have Splint 3.1.2 and compiled it myself because I had to insert some
hacks to let it analyze code for embedded systems. But I don't know how
to skip code completely in a save way. I tried /*@ignore@*/ /*@end@*/
too, but that doesn't work. It seems that it only doesn't output error
messages but parses the code normally.
Maybe someone has an idea how i can add a hack for this special thing,
or if there is another annotation. Please let me know. Thanks.

Best regards

Sebastian


From elfring at users.sourceforge.net  Tue Jan 29 00:39:23 2008
From: elfring at users.sourceforge.net (SF Markus Elfring)
Date: Tue, 29 Jan 2008 09:39:23 +0100
Subject: [splint-discuss] Skip code parts
Message-ID: <971354755@web.de>

> i want to skip code parts that are between "#pragma asm" and "#pragma
> endasm" because Splint ends with a parse error when it parses this code.

Did you try conditional compilation with the help from the prepropessor symbol "S_SPLINT_S" already?
http://splint.org/manual/html/sec14.html#_Toc534975037

Regards,
Markus

From jon.wilson at globalgraphics.com  Tue Jan 29 01:16:21 2008
From: jon.wilson at globalgraphics.com (Jon Wilson)
Date: Tue, 29 Jan 2008 09:16:21 +0000
Subject: [splint-discuss] Skip code parts
In-Reply-To: <49ED01FC03EE524BB7BB258E8F93BFF319A776@bfl-exchange-1.BFL.local>
References: <49ED01FC03EE524BB7BB258E8F93BFF319A776@bfl-exchange-1.BFL.local>
Message-ID: <479EEEE5.4@globalgraphics.com>

Matuschka, Sebastian wrote:
> Hi,
> 
> i want to skip code parts that are between "#pragma asm" and "#pragma
> endasm" because Splint ends with a parse error when it parses this code.
> I have Splint 3.1.2 and compiled it myself because I had to insert some
> hacks to let it analyze code for embedded systems. But I don't know how
> to skip code completely in a save way. I tried /*@ignore@*/ /*@end@*/
> too, but that doesn't work. It seems that it only doesn't output error
> messages but parses the code normally.
> Maybe someone has an idea how i can add a hack for this special thing,
> or if there is another annotation. Please let me know. Thanks.
> 
> Best regards
> 
> Sebastian

The easiest way is to hide it from splint with a "#ifndef S_SPLINT_S" 
conditional compilation section.

Cheers,

Jon

From Sebastian.Matuschka at gcd-solutions.de  Tue Jan 29 02:03:43 2008
From: Sebastian.Matuschka at gcd-solutions.de (Matuschka, Sebastian)
Date: Tue, 29 Jan 2008 11:03:43 +0100
Subject: [splint-discuss] [BUG] splint code
Message-ID: <49ED01FC03EE524BB7BB258E8F93BFF319A78B@bfl-exchange-1.BFL.local>

While adding some hacks in the splint sources i saw this code in
usymtab.c at line 2012:

	  if (c != ' ' || c != '\t') 
	    {
	      llbuglit ("Junk in load file");
	    }

I guess it should be &&, else this if is _always_ executed.

I looked into the latest source code release and it is still there
(usymtab.c line 2012).

Regards
Sebastian