Path: csiph.com!news.swapon.de!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.lang.c++
Subject: Re: ???Microsoft Azure CTO Mark Russinovich: C/C++ should be deprecated???
Date: Sun, 02 Oct 2022 07:24:31 -0700
Organization: A noiseless patient Spider
Lines: 23
Message-ID: <86lepyjobk.fsf@linuxsc.com>
References: <tgfn8d$1sr8e$1@dont-email.me> <tgjogc$1ivg$2@gioia.aioe.org> <tgk5qc$2h0hh$1@dont-email.me> <tgrnao$3gj$1@gioia.aioe.org> <tgs3un$3nr9v$1@dont-email.me> <tgsd4k$lcr$1@gioia.aioe.org> <tgufba$1dae$1@dont-email.me> <tgutm0$pp1$1@gioia.aioe.org> <20220927111408.394@kylheku.com> <7BIYK.100167$ocy7.42366@fx38.iad> <20220927165229.354@kylheku.com> <th0m63$a507$1@dont-email.me> <20220928012034.643@kylheku.com> <th1vf4$dfa0$1@dont-email.me> <20220928162825.705@kylheku.com> <th3pik$kpdd$1@dont-email.me> <20220929104930.67@kylheku.com> <th4p4g$nns9$1@dont-email.me> <20220930100037.560@kylheku.com> <thbt7p$1mgus$1@dont-email.me> <87sfk6qvtb.fsf@bsb.me.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader01.eternal-september.org; posting-host="ebe72c05e9167e1dd1c2f9bc3baee014"; logging-data="1809355"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19bty2h6/cyh2jAoLZFWKufFB7KkoF7vzY="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:Xy3XBEyjqUVUIoSMyRWRYX2lnv8= sha1:MoghIfoPNMUlVcY6vAwqg+jxAoY=
Xref: csiph.com comp.lang.c++:86761

Ben Bacarisse <ben.usenet@bsb.me.uk> writes:

> David Brown <david.brown@hesbynett.no> writes:
>
>> On 30/09/2022 19:20, Kaz Kylheku wrote:
>
> <cut>
>
>>> Speaking of returning the cross-posting to comp.lang.c++, that language
>>> as of C++17 has chosen to define some evaluation orders.
>>
>> Yes.  Primarily it is for the case of "cout << a() << b();".  This is
>> a situation where specific ordering really does help the programmer.
>
> I'm curious.  How does a specific ordering help the programmer here?
> Even with no specified order of evaluation, the output must look as if
> the result of b() was appended to the stream resulting from the
> left-most << operator.  All the ordering does is cause any side effects
> in a() and b() to be predictably ordered, and that might look more like
> helping the programmer to write dodgy code.

For this sub-thread I think the posting should have been limited
to comp.lang.c++, and not included comp.lang.c.