> I feel the proper way to prevent this and other "C" easy potential mistakes
> is to use a tool, a static code checker (i.e. lint). 

Yes!

> I use the open source LCLint which is included with most Linux distro's and
> next week will be changing over to its successor SPLint
> http://www.splint.org/. 

Thanks a lot! I didn't know there was an open source lint around. That'll
sure become a part of my C environment.

> Use a version control tool, my favorite is QVCS from Quma
> Software http://www.qumasoft.com/. 

I use cvsnt (http://cvsnt.org/) with TortoiseCVS as GUI client. Free and
pretty good. Not perfect, though.

Gerhard
_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist