Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!ateng!chip
From: chip@ateng.com (Chip Salzenberg)
Newsgroups: comp.lang.c
Subject: Re: This one bit me today
Message-ID: <254471D1.3533@ateng.com>
Date: 24 Oct 89 14:29:35 GMT
References: <2432@hub.UUCP> <568@sppy00.UUCP> <750@philmtl.philips.ca> <4147@ncsuvx.ncsu.edu> <267@wsl.UUCP> <244@bbxsda.UUCP> <1901@xyzzy.UUCP> <255@bbxsda.UUCP> <1949@xyzzy.UUCP> <273@bbxsda.UUCP> <2057@xyzzy.UUCP> <41019@bu-cs.BU.EDU>
Organization: A T Engineering, Tampa, FL
Lines: 28

According to austin@bucsf.bu.edu (Austin Ziegler):
>In Pascal, one of the nicest features for debugging is nested comments.

Of course, let us not forget that Pascal has two kinds of comment
delimiters, (* *) and { }, and that nesting { { } } or (* (* *) *) doesn't
work.  C has only /* */.

>This is provided as a *Debugging* feature *only* in Turbo C.  Nowhere does
>Borland state that you should use that feature in normal programming.

Nested comments are a _bug_, not a feature, Borland apologists
notwithstanding.

>I *have* found the need to comment it out because I am not fully
>acquainted with all of the features of the preprocessor commands.

Ignorance of the language is no excuse.  All that's needed is:

	#if 0
		/* never do this */
		system("delete *.*");
	#endif

-- 
You may redistribute this article only to those who may freely do likewise.
Chip Salzenberg at A T Engineering;  <chip@ateng.com> or <uunet!ateng!chip>
"'Why do we post to Usenet?'  Naturally, the answer is, 'To get a response.'"
                        -- Brad "Flame Me" Templeton