Undefined behavior and sequence points reloaded

by

It looks like the code

i.operator+=(i.operator ++());

Works perfectly fine with regards to sequence points. Section 1.9.17 of the C++ ISO standard says this about sequence points and function evaluation:

When calling a function (whether or not the function is inline), there is a sequence point after the evaluation of all function arguments (if any) which takes place before execution of any expressions or statements in the function body. There is also a sequence point after the copying of a returned value and before the execution of any expressions outside the function.

This would indicate, for example, that the i.operator ++() as the parameter to operator += has a sequence point after its evaluation. In short, because overloaded operators are functions, the normal sequencing rules apply.

Great question, by the way! I really like how you’re forcing me to understand all the nuances of a language that I already thought I knew (and thought that I thought that I knew). 🙂

More Related Contents:

  1. Undefined behavior and sequence points
  2. What are all the common undefined behaviours that a C++ programmer should know about? [closed]
  3. C++ delete – It deletes my objects but I can still access the data?
  4. Why can templates only be implemented in the header file?
  5. “std::endl” vs “\n”
  6. What is the difference between public, private, and protected inheritance in C++?
  7. Accessing inactive union member and undefined behavior?
  8. What’s the difference between “STL” and “C++ Standard Library”?
  9. Best practices for circular shift (rotate) operations in C++
  10. What XML parser should I use in C++? [closed]
  11. Does initialization entail lvalue-to-rvalue conversion? Is `int x = x;` UB?
  12. What are the new features in C++17?
  13. What’s a proper way of type-punning a float to an int and vice-versa?
  14. What does it mean to have an undefined reference to a static member?
  15. What C++ Smart Pointer Implementations are available?
  16. Why do I see strange values when I print uninitialized variables?
  17. Is the ‘override’ keyword just a check for a overridden virtual method?
  18. Why are my struct’s members not properly initialised using `{}`? [duplicate]
  19. gcc/g++: “No such file or directory”
  20. Are multiple mutations within initializer lists undefined behavior?
  21. A C++ implementation that detects undefined behavior?
  22. Why do we actually need Private or Protected inheritance in C++?
  23. Why does the enhanced GCC 6 optimizer break practical C++ code?
  24. Why is it that we can write outside of bounds in C?
  25. Is infinite loop still undefined behavior in C++ if it calls shared library?
  26. Mixing class and struct
  27. Is it allowed to cast away const on a const-defined object as long as it is not actually modified?
  28. Can branches with undefined behavior be assumed unreachable and optimized as dead code?
  29. behavior of const_cast in C++ [duplicate]
  30. Can undefined behavior erase the hard drive?

Leave a Comment