Date: Fri, 25 Apr 2003 05:49:35 +0100 From: Jonathon McKitrick <jcm@FreeBSD-uk.eu.org> To: Dag-Erling Smorgrav <des@ofug.org> Cc: freebsd-chat@freebsd.org Subject: Re: Code layout and debugging time Message-ID: <20030425044935.GG81840@dogma.freebsd-uk.eu.org> In-Reply-To: <xzp3ck8gac2.fsf@flood.ping.uio.no> References: <20030422132906.GB64101@dogma.freebsd-uk.eu.org> <444r4qmp6n.fsf@be-well.ilk.org> <20030422172549.GA65023@dogma.freebsd-uk.eu.org> <xzp3ck8gac2.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 23, 2003 at 11:42:05PM +0200, Dag-Erling Smorgrav wrote: : That is way too much, and bde would have your nads for breakfast if : you committed anything like that. Who is bde, again? : Simply put, too much whitespace is just as bad as no whitespace at : all. Imagine reading a book where every sentence is a separate : paragraph; paragraph breaks become worthless because they no longer : serve to group sentences together. True, yet a lot of the kernel code and driver code does just that: extensive commenting, even when it only means one line of code. jcm -- Consulting: If you aren't part of the solution, there is a lot of money to be made in prolonging the problem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030425044935.GG81840>