Sam Clippinger wrote on 2011-09-03 01:08:
> I'll get right on that. :) Personally I find the code to be quite
> readable, except in a few places where the technical needs outweigh
> the human needs (e.g. configuration.c and dns.c) -- in those places
> you'll find comments. :) In general all my code is pretty bare of
> comments, because they increase the maintenance work (update the
> code, then update the comments)
Not really, because I do not mean
/* so long and detailed comments each
** line, that you get them out and
** publish in 20 volumes as they are
** that damn big, so anyone would be
** able to write code just based on
** that 'recipe' */
I rather mean one-liners in important parts like
// can we do this with that
if( .... )
{
[code]
// now we done so we set tell the callee what to do next
set_rejection(....)
}
else
{
// no, we cant. this usually means that..
..
}
also it helps to have commonly function documented a bit more
like, so we know what each argument means and why to use it properly.
Like said set_rejection()
This does not increase mainteace of the code nor eats more time
to produce the code.
Regards,
--
"Daddy, what "Formatting drive C:" means?"...
Marcin http://wfmh.org.pl/carlos/
_______________________________________________
spamdyke-users mailing list
[email protected]
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
