PC Lint vs. splint

JeanneP wrote:

> I'm asking because we have code that's shared across multiple projects.
> When you check in a file that is used by another project, that project
> gets updated too. The advanages are that everyone gets to benefit from
> the updates right away, but the downsides are that what works in one
> project may break another. Maybe someone used a #defined value from a
> non-shared file in a shared file, or something similar. Folks usually
> don't bother building all of the other projects that share their file
> before checking in code, due to looming deadlines on their own projects.
> They usually get away with it, but it sure can be a headache when you
> have to make sure updating your sandbox won't cause a break before you
> actually update it.  It's impractical to ask people to always check
> every affected build before checking in updates, because it would take
> several hours to build every flavor of every project, during which time
> there may have been more updates. Of course we have an automated builder
> so it doesn't get out of control. But, if lint is fast enough, people
> could lint the other projects before checking in their code.
 
Sounds like you may also benefit from installing a decent version control 
system with sand-boxing capabilities. That way you would not affect the 
other projects in a haphazard way. They could get to benefit from updates 
of the common source tree when they were good and ready for it.


-- 
********************************************************************
Paul E. Bennett ....................<email://peb@a...>
Forth based HIDECS Consultancy .....<http://www.amleth.demon.co.uk/>
Mob: +44 (0)7811-639972 .........NOW AVAILABLE:- HIDECS COURSE......
Tel: +44 (0)1235-811095 .... see http://www.feabhas.com for details.
Going Forth Safely ..... EBA. www.electric-boat-association.org.uk..
********************************************************************

On Wed, 24 Nov 2004 18:06:52 +0000, "Paul E. Bennett"
<peb@amleth.demon.co.uk> wrote:
>Sounds like you may also benefit from installing a decent version control 

Check out subversion: http://subversion.tigris.org/

(And it's free.)


-- 
#include <standard.disclaimer>
 _
Kevin D Quitt  USA 91387-4454         96.37% of all statistics are made up
  Per the FCA, this address may not be added to any commercial mail list

jpetrang@harris.com (JeanneP) wrote:

[PC-Lint vs. splint]

>Has anyone been so dissatisfied with splint that they switched to 
>PC Lint, and did PC Lint solve the problem(s) that caused the 
>dissatisfaction?

Yes, me. Splint has (had?) problems with some non-ANSI (legacy)
"extensions" of embedded compilers. Look at the Splint mailing list
archive or search for my posting here dated 2003-05-17, Message-ID
<3ec5f992.373447@z1.oliverbetz.de>.

And the already mentioned problems when assigning literals to U8 are
really annoying in embedded environments where this happens often.

Oliver
-- 
Oliver Betz, Muenchen (oliverbetz.de)

"Grant Edwards" <grante@visi.com> wrote in message
news:41a3e059$0$85085$a1866201@visi.com...
> On 2004-11-24, Dave Hansen <iddw@hotmail.com> wrote:
>
> I'm also alergic to node-locked stuff.  I've been burned too
> many times when a motherboard, disk drive, or whatnot died and
> I had to cough up a pile of cash for the privledge of running a
> program I already paid for once.
>

If the company even exists by the time that happens!

It's too bad there's not a law requiring companies discontinuing software
known to be in current use to place it in the public domain...

Rufus