Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!bionet!apple!agate!ucbvax!tut.cis.ohio-state.edu!purdue!bu-cs!spike
From: spike@bu-cs.BU.EDU (Spike)
Newsgroups: gnu.gcc
Subject: Re: spotting syntax errors
Message-ID: <34605@bu-cs.BU.EDU>
Date: 13 Jul 89 01:26:16 GMT
References: <YYivPOy00WB4Q9X41M@andrew.cmu.edu>
Reply-To: spike@buit4.bu.edu (Joe Ilacqua)
Followup-To: gnu.gcc
Distribution: gnu
Organization: Software Tool & Die
Lines: 16

In article <YYivPOy00WB4Q9X41M@andrew.cmu.edu> sr16+@ANDREW.CMU.EDU (Seth Benjamin Rothenberg) writes:
<I recently tried to compile a program with an unclosed comment in it.
	[...]
<I thought of a simple was to trap this error.
<Since nested comments generally do cause errors, they should
<be disallowed.  Thus, when the compiler spots a nested comment,
<it could flag it, including a pointer to original (unclosed) comment.

	From the gcc man page (and of course in the info file):

     -Wcomment
          Warn whenever a comment-start sequence `/*' appears  in
          a comment.

->Spike
Software Tool & Die     The right choice.