Path: csiph.com!news.swapon.de!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: Thu, 05 Apr 2018 11:23:07 -0700 Organization: None to speak of Lines: 24 Message-ID: References: <9c7013a2-17bd-4f94-a378-1c45151d0d45@googlegroups.com> <6zpxC.75432$bz1.69868@fx01.iad> <%6sxC.621528$Ml.294897@fx24.am4> <85txC.105783$q15.11321@fx34.iad> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="7bf2a82357868b78051038e61a1f9d6f"; logging-data="22491"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/hJeZUpj2lQdzhXjier6Bf" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:OBJXo8WnWGaVrHFjpU2276csbZ8= sha1:zmc4wHbZa+1rZq3v0fR16FkIcrM= Xref: csiph.com comp.lang.c:128796 bartc writes: [...] > With C, the \ exists in part of source which is the domain of the > comment text. \ characters can exist in // comments without forming line > continuation. A \ becomes a line continuation only if there are zero or > more spaces or tabs between the \ and the newline. N1570 5.1.1.2, translation phase 2: Each instance of a backslash character (\) immediately followed by a new-line character is deleted, splicing physical source lines to form logical source lines. My understanding is that "immediately followed" means there can't be any spaces between the backslash and the new-line. gcc and clang apparently disagree with me on this point. [...] -- 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"