C++ order of evaluation of operands, arguments

[Andrew Haley]

On 11/25/2015 06:25 PM, Martin Sebor wrote:
> The motivating example in the paper suggests that many C++
> programmers expect a left to right order of evaluation here
> due to the commonality of constructs like chains of calls.

Sure, I often see

  foo.bar(1).bar(2).bar(3), etc.

but does anyone actually do

  foo(1)bar(2)bar(3)  ?

That's what I'm talking about.

Andrew.