← Back to context Comment by weinzierl 11 hours ago A fun one that'd fit list be sequence point violations like i = i++ 4 comments weinzierl Reply radiospiel 11 hours ago Fun, sure, but also GCC and Clang will both warn with -Wall (-Wsequence-point / -Wunsequenced). account42 8 hours ago This would also be a code smell even if it was well defined. marcosdumay 18 minutes ago Yes, it should be an explicit error. Not undefined. leni536 9 hours ago Only in C, that one is defined in C++.edit: I'm not sure it's even undefined in C.
radiospiel 11 hours ago Fun, sure, but also GCC and Clang will both warn with -Wall (-Wsequence-point / -Wunsequenced).
account42 8 hours ago This would also be a code smell even if it was well defined. marcosdumay 18 minutes ago Yes, it should be an explicit error. Not undefined.
leni536 9 hours ago Only in C, that one is defined in C++.edit: I'm not sure it's even undefined in C.
Fun, sure, but also GCC and Clang will both warn with -Wall (-Wsequence-point / -Wunsequenced).
This would also be a code smell even if it was well defined.
Yes, it should be an explicit error. Not undefined.
Only in C, that one is defined in C++.
edit: I'm not sure it's even undefined in C.