Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: "C's Biggest Mistake" Date: Sun, 15 Apr 2018 12:39:24 -0700 Organization: None to speak of Lines: 24 Message-ID: References: <%6sxC.621528$Ml.294897@fx24.am4> <85txC.105783$q15.11321@fx34.iad> <_MIzC.1013644$Ly1.422539@fx13.am4> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="c89b1d935abe804b720146da5cf99024"; logging-data="26517"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18actQL9AV/cdcMzVzQYFxl" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:dbvropP35hn2moPdrk4/MEAxiNI= sha1:3mj/iZxUSaBHoHjujaknCE7t8zY= Xref: csiph.com comp.lang.c:129233 Ike Naar writes: > On 2018-04-14, Keith Thompson wrote: >> A PL/I grammar I found says: >> >> comments = "/*" [ text ] "*/" >> >> "text" is not defined, but presumably it can include "*/", which >> again implies that comments do not nest. > > Do you mean "can include", or "can't include"? > If [text] can include '*/', then what would terminate a [text] ? Hmm. I didn't quite think that through. Taken literally, it would imply that a comment would be terminated only by the end of the file (which obviously is not the intent). I think it's meant to imply that the first occurrence of "*/" terminates the comment. It could have been stated more clearly. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"