Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Newsgroups | comp.std.c |
| Subject | Re: Adjacent string literals |
| Date | 2021-07-22 10:29 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <86im125kaq.fsf@linuxsc.com> (permalink) |
| References | <rumnae$4mr$1@dont-email.me> <86v95i88zw.fsf@linuxsc.com> <87fswl7rvg.fsf@nosuchdomain.example.com> |
Keith Thompson <Keith.S.Thompson+u@gmail.com> writes: > Tim Rentsch <tr.17687@z991.linuxsc.com> writes: > >> James Kuyper <jameskuyper@alumni.caltech.edu> 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". That's consistent with what I said: "adjoining" being only one of the definitions is consistent with saying "adjacent" doesn't _always_ mean touching. Words in English can be ambiguous in their meanings. > 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, In the case of hotels I think "adjoining" always means connected, either with or perhaps without a door, but yes. > 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 better example is a small utility closet rather than an elevator. "Adjacent" usually implies "closeness" even if it doesn't always mean touching, and two rooms with a bank of four elevators between them would for most people not be considered adjacent, I think. In the case of hotel rooms at least it's a matter of degree. Another example is two rooms having the same latitude and longitude, but on different (consecutive) floors. I think most people wouldn't call those rooms "adjacent". However, if there is a connecting stairway between them, a hotel might very well offer them as "adjoining rooms". > 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. Given that the wording lasted more than 30 years without anyone even noticing a problem, I think the case for leaving it alone is decidedly stronger than the case for making a change.
Back to comp.std.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Adjacent string literals James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-01-25 10:15 -0500
Re: Adjacent string literals Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-26 12:22 +0000
Re: Adjacent string literals Jakob Bohm <jb-usenet@wisemo.com.invalid> - 2021-01-26 13:48 +0100
Re: Adjacent string literals Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-01-26 13:05 -0800
Re: Adjacent string literals Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-26 21:40 +0000
Re: Adjacent string literals Jakob Bohm <jb-usenet@wisemo.com.invalid> - 2021-01-28 09:53 +0100
Re: Adjacent string literals James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-01-28 05:45 -0500
Re: Adjacent string literals Richard Damon <Richard@Damon-Family.org> - 2021-01-26 07:52 -0500
Re: Adjacent string literals James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-01-26 09:29 -0500
Re: Adjacent string literals Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-26 21:46 +0000
Re: Adjacent string literals James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-01-26 18:28 -0500
Re: Adjacent string literals Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-27 01:16 +0000
Re: Adjacent string literals James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-01-26 22:48 -0500
Re: Adjacent string literals Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-27 15:46 +0000
Re: Adjacent string literals James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-01-27 11:20 -0500
Re: Adjacent string literals Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-28 03:05 +0000
Re: Adjacent string literals Tim Rentsch <tr.17687@z991.linuxsc.com> - 2021-07-10 08:49 -0700
Re: Adjacent string literals Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-07-10 14:58 -0700
Re: Adjacent string literals Tim Rentsch <tr.17687@z991.linuxsc.com> - 2021-07-22 10:29 -0700
Re: Adjacent string literals James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-07-11 11:41 -0700
Re: Adjacent string literals Tim Rentsch <tr.17687@z991.linuxsc.com> - 2021-07-22 15:26 -0700
Re: Adjacent string literals James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-07-22 17:29 -0700
Re: Adjacent string literals Tim Rentsch <tr.17687@z991.linuxsc.com> - 2022-01-17 05:29 -0800
csiph-web