Path: csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.std.c Subject: Re: Adjacent string literals Date: Sat, 10 Jul 2021 14:58:59 -0700 Organization: None to speak of Lines: 37 Message-ID: <87fswl7rvg.fsf@nosuchdomain.example.com> References: <86v95i88zw.fsf@linuxsc.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: reader02.eternal-september.org; posting-host="7dee47812cca3c2bd649333529ffcd37"; logging-data="14108"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19YqcvLyud/rgwEo1jT7PHK" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) Cancel-Lock: sha1:ErOOQYi1kYbZ8Q5NiSnAczofC+E= sha1:9gFyol66raMyMrYR4vSST+eRKZs= Xref: csiph.com comp.std.c:6268 Tim Rentsch writes: > James Kuyper writes: [...] >> If the phrase "White-space characters separating tokens are no longer >> significant." were moved from the beginning of the description of phase >> 7 to the beginning of the description phase 6, it would make the >> insignificance of white space separating string literals perfectly >> clear, and as far as I can see, would have no other effect > > The word "adjacent" doesn't alway mean touching. There is another > word for that, the word "adjoining". Booking a hotel reservation > for adjacent rooms is not the same as a reservation for adjoining > rooms. That's not entirely clear. dictionary.com (not a definitive reference but a convenient one) shows "adjoining" as one of the definitions of "adjacent". If I understand you correctly, if rooms 110 and 112 share a common wall, perhaps with a door going between them, they're both adjacent and adjoining, but if instead they're on opposide sides of the elevator they're adjacent but not adjoining. Is that what you meant? I'm not sure I'd call them "adjacent" in that case. A footnote on "Adjacent string literals are concatenated" saying that two string literals are adjacent if they're adjoining or separated only by white-space characters would clear this up. Moving "White-space characters separating tokens are no longer significant." from the beginning of phase 7 to the beginning of phase 6 would also be a good solution. But given the clear examples, I wouldn't object to leaving it as it is. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com Working, but not speaking, for Philips void Void(void) { Void(); } /* The recursive call of the void */