Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #169219
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: lvalue assignment difference between C and C++ |
| Date | 2023-02-07 16:25 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <871qn1mohw.fsf@bsb.me.uk> (permalink) |
| References | <trltmg$21cft$1@dont-email.me> <0mvDL.68810$b7Kc.34465@fx39.iad> <20230206141733.165@kylheku.com> <87mt5qe7pc.fsf@nosuchdomain.example.com> <0f9840b3-7421-47ae-a507-0069cbfed700n@googlegroups.com> |
Paul N <gw7rib@aol.com> writes: > On Monday, February 6, 2023 at 10:43:27 PM UTC, Keith Thompson wrote: >> Kaz Kylheku <864-11...@kylheku.com> writes: >> > On 2023-02-04, Richard Damon <Ric...@Damon-Family.org> wrote: >> >> The key difference is that in C, the results of the conditional operator >> >> is always an r-value, and thus not suitable for an assignment operator. >> > >> > Interestingly, unlike C++, ISO C doesn't use the term rvalue (only >> > lvalue). However: the term was used in the reference manual for the B >> > language, predecessor to C. >> > >> > A footnote (I'm looking at C99, where it is note #53 on P. 46) says >> > "What is sometimes called ‘‘rvalue’’ is in this International Standard >> > described as the ‘‘value of an expression’’." >> > >> > Every regular here knows this trivia; just dredging it up a bit here. >> Right, and the way C (non-normatively) defines "rvalue" is a bit odd. >> An lvalue is a kind of expression, but an rvalue is the result of >> evaluating an expression. >> >> Historically, lvalues and rvalues were kinds of values. An expression >> could be "evaluated for its lvalue" or "evaluated for its rvalue", >> depending on the context in which it appears. In particular, the left >> hand side of an assignment is evaluated for its lvalue (the identify of >> the object it designates), and the right hand side of an assignment is >> evaluated for its rvalue. Some expressions, such as 42, have rvalues >> but not lvalues; thus 42 cannot appear on the LHS of an assignment. >> This probably goes back to BCPL, or perhaps even CPL. > > Yes, that is how it worked in BCPL. In fact, BCPL has keywords LV and > RV which can be used to evaluate an expression in its other context, That was very early BCPL. By the time the book was published (and when I first used it) all references to rvalues and lvalues had gone! I think the very detailed distinction made early on was probably a hangover from CPL and was subsequently found to be unnecessarily fussy. > but the symbols @ and ! can also do this - I guess the symbols were > added later and people used them instead, The early manual (with _lv_ and _rv_ operators) is of the old-school type where the syntax is given using presentation symbols (often underlined) that will map to some concrete representation in a particular implementation. I never used BCPL that old, so I don't know what was used for _rv_ and _lv_ in practice. Other underlined symbols were usually written in upper case so I'd guess RV and LV. Did you use (or even see) BCPL of the era? Though off-topic, I'd love to see some! I'm not 100% sure that the later @ (essentially "address-of") and unary ! (essentially "dereference") are exactly what the 1967 manual writes as _rv_ and _lv_. There are enough other differences in that early version (and the example code at the end is sadly missing) for it to be unclear, at least to me. Do you know if they were, in fact, just concrete representations of those keywords? > leading to C's @ and *. You mean C's & and *. In the later BCPL, ! was also binary with a!b being, essentially, C's a[b]. Early BCPL (which is the form that influenced B and C) used the very clumsy a*[b] form because []s were also used for function calls. That syntax, sin[pi], definitely comes from CPL. -- Ben.
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
lvalue assignment difference between C and C++ Muttley@dastardlyhq.com - 2023-02-04 15:30 +0000
Re: lvalue assignment difference between C and C++ Richard Damon <Richard@Damon-Family.org> - 2023-02-04 11:04 -0500
Re: lvalue assignment difference between C and C++ Muttley@dastardlyhq.com - 2023-02-04 16:59 +0000
Re: lvalue assignment difference between C and C++ Richard Damon <Richard@Damon-Family.org> - 2023-02-04 13:02 -0500
Re: lvalue assignment difference between C and C++ Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-04 12:45 -0800
Re: lvalue assignment difference between C and C++ David Brown <david.brown@hesbynett.no> - 2023-02-05 11:42 +0100
Re: lvalue assignment difference between C and C++ Muttley@dastardlyhq.com - 2023-02-06 09:26 +0000
Re: lvalue assignment difference between C and C++ David Brown <david.brown@hesbynett.no> - 2023-02-06 14:13 +0100
Re: lvalue assignment difference between C and C++ Muttley@dastardlyhq.com - 2023-02-06 15:50 +0000
Re: lvalue assignment difference between C and C++ David Brown <david.brown@hesbynett.no> - 2023-02-06 20:08 +0100
Re: lvalue assignment difference between C and C++ Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-06 12:47 -0800
Re: lvalue assignment difference between C and C++ Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-06 13:03 -0800
Re: lvalue assignment difference between C and C++ Muttley@dastardlyhq.com - 2023-02-07 09:24 +0000
Re: lvalue assignment difference between C and C++ Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-07 11:08 -0800
Re: lvalue assignment difference between C and C++ Muttley@dastardlyhq.com - 2023-02-08 09:23 +0000
Re: lvalue assignment difference between C and C++ Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-02-08 22:13 -0500
Re: lvalue assignment difference between C and C++ James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-02-08 22:53 -0500
Re: lvalue assignment difference between C and C++ Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-08 22:12 -0800
Re: lvalue assignment difference between C and C++ Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-02-08 02:52 +0000
Re: lvalue assignment difference between C and C++ Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-06 09:11 +0200
Re: lvalue assignment difference between C and C++ Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-06 01:01 -0800
Re: lvalue assignment difference between C and C++ Richard Damon <Richard@Damon-Family.org> - 2023-02-06 07:42 -0500
Re: lvalue assignment difference between C and C++ Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-06 12:59 -0800
Re: lvalue assignment difference between C and C++ bart c <bart4858@gmail.com> - 2023-02-06 08:11 -0800
Re: lvalue assignment difference between C and C++ Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-02-06 21:19 +0000
Re: lvalue assignment difference between C and C++ Bonita Montero <Bonita.Montero@gmail.com> - 2023-02-07 07:44 +0100
Re: lvalue assignment difference between C and C++ Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-07 09:18 +0200
Re: lvalue assignment difference between C and C++ Kaz Kylheku <864-117-4973@kylheku.com> - 2023-02-06 22:21 +0000
Re: lvalue assignment difference between C and C++ Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-06 14:43 -0800
Re: lvalue assignment difference between C and C++ Paul N <gw7rib@aol.com> - 2023-02-07 03:17 -0800
Re: lvalue assignment difference between C and C++ Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-02-07 16:25 +0000
Re: lvalue assignment difference between C and C++ Paul N <gw7rib@aol.com> - 2023-02-08 13:19 -0800
Re: lvalue assignment difference between C and C++ Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-02-08 23:46 +0000
Re: lvalue assignment difference between C and C++ Bonita Montero <Bonita.Montero@gmail.com> - 2023-02-04 19:41 +0100
Re: lvalue assignment difference between C and C++ Andrey Tarasevich <andreytarasevich@hotmail.com> - 2023-02-10 16:19 -0800
csiph-web