<html>
<head>
<style>
P
{
margin:0px;
padding:0px
}
body
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body>Don't forget to use lint if you are writing C code and valgrind is handy too.<BR>
<BR>
See:<BR>
<A href="http://www.splint.org/">http://www.splint.org/</A><BR>
<BR>
Though the best by a mile is Gimpel's Flexelint (costly but obfuscated source) or PCLint (about 170 quid but runs under wine as well as DOS, OS/2, Win32).<BR>
<BR>
Mike<BR><BR><BR><BR><BR><BR>
<HR id=stopSpelling>
<BR>
> From: b_whelan@mistral.co.uk<BR>> To: sussex@mailman.lug.org.uk<BR>> Subject: Re: [Sussex] Code-writing methods<BR>> Date: Fri, 17 Nov 2006 11:17:20 +0000<BR>> <BR>> I agree that comments are vital where something is complicated or a "clever"<BR>> bit of code is included. Almost all programs need to be changed, extended or<BR>> the code re-used at some point. If I pick up one of my own programs after<BR>> several months, or even years, I find that the comments help.<BR>> <BR>> Programming languages vary and hence the amount of commenting needed should<BR>> be adjusted accordingly. I would suggest that PHP is an easier, and more<BR>> intuitive, language to learn that C. I first wrote a program in about 1968<BR>> using punched cards and FORTRAN II. (For the historians amongst you, I never<BR>> actually knew Charles Babbage but Ada Lovelace was a close friend). My<BR>> advice would be to choose a good language, keep code simple and adopt a<BR>> straightforward logical structure. That way you will be able to understand<BR>> your own programs and have others maintain them economically.<BR>> <BR>> Brendan<BR>> <BR>> <BR>> <BR>> __ <BR>> Sussex mailing list<BR>> Sussex@mailman.lug.org.uk<BR>> E-mail Address: sussex@mailman.lug.org.uk<BR>> Sussex LUG Website: http://www.sussex.lug.org.uk/<BR>> https://mailman.lug.org.uk/mailman/listinfo/sussex<BR><BR><br /><hr />Be one of the first to try <a href='http://ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0e-4911fb2b2e6d' target='_new'>Windows Live Mail.</a></body>
</html>