Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!novavax!twwells!bill
From: bill@twwells.uucp (T. William Wells)
Newsgroups: comp.misc
Subject: Re: Program Errors and developement environment
Message-ID: <782@twwells.uucp>
Date: 14 Mar 89 18:41:20 GMT
References: <4352@enea.se> <2950@hound.UUCP> <3998@ttidca.TTI.COM> <756@twwells.uucp> <4032@ttidca.TTI.COM>
Reply-To: bill@twwells.UUCP (T. William Wells)
Organization: None, Ft. Lauderdale
Lines: 35
Summary:
Expires:
Sender:
Followup-To:
Distribution:
Keywords:

In article <4032@ttidca.TTI.COM> hollombe@ttidcb.tti.com (The Polymath) writes:
: I don't want to debate either, but several people, including you, seem to
: have missed my original point, so I'll try to improve my explanation.
:
: I'm not worried about unterminated comments so much as un-noticed comments.
: When you've got something like
:
: [much crufty code]
: /*
: [much crufty code commented out]
: */
: [much more crufty code]
:
: It's very easy to miss the fact that those middle lines aren't live code.
: That can cause you to waste time trying to fix them or wondering why code
: you've added to them doesn't work.

I agree. That is why I'd do the above as:

	[much crufty code]
#ifdef notdef
	[much crufty code commented out]
#endif
	[much more crufty code]

Using defines works, first, even if there are comments in the middle
section, and second, is trivial to spot.

So I stand by my original statement.

---
Bill
{ uunet | novavax } !twwells!bill
(BTW, I'm going to be looking for a new job sometime in the next
few months.  If you know of a good one, do send me e-mail.)