> Unlike Andrew, I do believe one can have too many comments.
How about keeping the comments somewhat separate from the code?
Let the code tell its own story, for those who want to read code. Let
the comments explain the overall goals and strategy, and perhaps a key
detail or two that might be confusing.
But don't intermingle the two line by line. They are as two different
languages, that speak to different people, and different parts of the
brain of the bi-lingual.
Make it visually easy for each reader to filter out the 'other stuff.'
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj _at_ sgi.com> 1.650.933.1373
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo _at_ vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
References:
- Re: seperator error in __mask_snprintf_lenPaul Jackson
- Re: seperator error in __mask_snprintf_lenJoe Korty
- Re: seperator error in __mask_snprintf_lenPaul Jackson
- Re: seperator error in __mask_snprintf_lenAndrew Morton
- Re: seperator error in __mask_snprintf_lenJoe Korty
- Re: seperator error in __mask_snprintf_lenPaul Jackson
- Re: seperator error in __mask_snprintf_lenMatthew Dobson
- [PATCH] bitmap parsing routines, version 3Joe Korty
- [PATCH] bitmap parsing/printing routines, version 4Joe Korty
- Re: [PATCH] bitmap parsing/printing routines, version 4Matthew Dobson
- Re: [PATCH] bitmap parsing/printing routines, version 4Joe Korty
- Prev by Date: Re: [PATCH] i2o_core.c, i2o_scsi.c minor bugfixes
- Next by Date: Re: [2.6][smbfs] smb_open & smb_readpage_sync errors in kernel log
- Previous by thread: Re: [PATCH] bitmap parsing/printing routines, version 4
- Next by thread: Re: [PATCH] bitmap parsing/printing routines, version 4
- Indexes:[Main][Thread]