Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c++ > #67202 > unrolled thread

Re: TIL: C++17 sequences assignment the wrong way.

Back to article view | Back to comp.lang.c++

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: TIL: C++17 sequences assignment the wrong way. Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-07-30 07:22 -0700
    Re: TIL: C++17 sequences assignment the wrong way. Keith Thompson <kst-u@mib.org> - 2019-07-30 13:08 -0700
      Re: TIL: C++17 sequences assignment the wrong way. Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-08-09 10:36 -0700

#67202 — Re: TIL: C++17 sequences assignment the wrong way.

ram@zedat.fu-berlin.de (Stefan Ram) writes:

> Newsgroups: comp.lang.lisp,comp.lang.c++
>
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> Do you happen to have a reference to this part of the spec?
>
> In the most recent draft, n4800, it's 7.6.18p1:
>
>    The right operand is sequenced before the left operand.
>    
>       . The assignment stores the value of the right operand
>       into the object indicated by the left operand, so the
>       operations involved are:
>    
>         First, obtain the value of the right operand,
>         then, store this value into the left operand.
>
> Therefore some kind of right-to-left sequencing is part
> of the semantics the assignment already always had, in
> any language.

This summary sentence is utter nonsense.

[toc] | [next] | [standalone]

#67210

Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
> ram@zedat.fu-berlin.de (Stefan Ram) writes:
>
>> Newsgroups: comp.lang.lisp,comp.lang.c++
>>
>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>
>>> Do you happen to have a reference to this part of the spec?
>>
>> In the most recent draft, n4800, it's 7.6.18p1:
>>
>>    The right operand is sequenced before the left operand.
>>    
>>       . The assignment stores the value of the right operand
>>       into the object indicated by the left operand, so the
>>       operations involved are:
>>    
>>         First, obtain the value of the right operand,
>>         then, store this value into the left operand.
>>
>> Therefore some kind of right-to-left sequencing is part
>> of the semantics the assignment already always had, in
>> any language.
>
> This summary sentence is utter nonsense.

What does the phrase "This summary sentence" refer to?

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Will write code for food.
void Void(void) { Void(); } /* The recursive call of the void */

[toc] | [prev] | [next] | [standalone]

#67499

Keith Thompson <kst-u@mib.org> writes:

> Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
>
>> ram@zedat.fu-berlin.de (Stefan Ram) writes:
>>
>>> Newsgroups: comp.lang.lisp,comp.lang.c++
>>>
>>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>>
>>>> Do you happen to have a reference to this part of the spec?
>>>
>>> In the most recent draft, n4800, it's 7.6.18p1:
>>>
>>>    The right operand is sequenced before the left operand.
>>>
>>>       . The assignment stores the value of the right operand
>>>       into the object indicated by the left operand, so the
>>>       operations involved are:
>>>
>>>         First, obtain the value of the right operand,
>>>         then, store this value into the left operand.
>>>
>>> Therefore some kind of right-to-left sequencing is part
>>> of the semantics the assignment already always had, in
>>> any language.
>>
>> This summary sentence is utter nonsense.
>
> What does the phrase "This summary sentence" refer to?

The sentence that starts "Therefore some kind of ...".

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.c++

csiph-web