I have a C++ learning demo here:
char c = \'M\';
short s = 10;
long l = 1002;
char * cptr = &c;
short * sptr = &s;
long * lptr = &l;
cout <&
According to C++ Standard Draft Paper N4762 (2018-07-07) on page 68 in section § 6.8.1/10
( or [intro.execution]/10 on eel.is website here )
Except where noted, evaluations of operands of individual operators and of subexpressions of individual expressions are unsequenced.
For statement
cout << c << '\t' << static_cast(cptr) << '\t' << static_cast(++cptr) << '\n';
that means c++ compiler can not guarantee that static_cast
will be evaluated before ++cptr
on the right because they are all operands on the same statement.
So you can force their sequential order of execution simply by ordering them in ordered and separated statements.
For example :
cout << c << '\t' << static_cast(cptr) << '\t'; cout << static_cast(++cptr) << '\n';
[ compiler explorer ]
As M.M's answer states that c++17 now guarantees operand evaluation sequence of <<
It turns out that GCC 8.1 doesn't warn, even with std=c++11
, unless with -Wall
and always warns with -Wall
While clang 6.0 warns "no matter what".
[ compiler explorer ]
So, as well as -std=c++17
, you must also provide option -Wno-unsequenced
to suppress it :
-Wall