Date: Tue, 22 Apr 2003 13:25:35 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Colin Percival <colin.percival@wadham.ox.ac.uk> Cc: freebsd-chat@freebsd.org Subject: Re: Code layout and debugging time Message-ID: <3EA5A53F.3016395C@mindspring.com> References: <5.0.2.1.1.20030422171035.01c5e258@popserver.sfu.ca> <5.0.2.1.1.20030422205617.0387b378@popserver.sfu.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Colin Percival wrote: > At 12:14 22/04/2003 -0700, Terry Lambert wrote: > >I think that there would not be a similar effect, unless the > >comments were sprinkled throughout the code like pixie dust. > >8-). [snip] > >If you ever find and Open Source that qualifies as "heavily > >commented", let us know, and we can go take a look. > > Well, not Open Source, but I have seen quite a few undergraduate > programming assignments which have "pixie dust" comments. Some people take > their instructors' advice to "comment everything you write" a bit too > seriously, I think. It could also be a matter of "available tools"; for example, people with comment-folding editors will be much more likely to comment the bejesus out of things, and make them unreadable to people without the same tools. Or people with Emacs will make code unreadable to everyone else... 8-) 8-) }B^). People with "vi" (and people who know how to use "grep") tend to declare functions: int foo(void) Rather than: int foo(void) Because they can search for declarations of a single function in a large amount of source code by anchoring the search to the start of the line... e.g.: cd /usr/src/sys find . -type f | xargs grep \^pmap_enter ...Of course, that's just because they haven't learned about "tags" files yet, I think... 8-) 8-O }B^). -- Terry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EA5A53F.3016395C>