Order of evaluation in C++ function parameters

by

No, there’s no such guarantee. It’s unspecified according to the C++ standard.

Bjarne Stroustrup also says it explicitly in “The C++ Programming Language” 3rd edition section 6.2.2, with some reasoning:

Better code can be generated in the
absence of restrictions on expression
evaluation order

Although technically this refers to an earlier part of the same section which says that the order of evaluation of parts of an expression is also unspecified, i.e.

int x = f(2) + g(3);   // unspecified whether f() or g() is called first

More Related Contents:

  1. Using paragraphs 8.5.3p4 and p5 in the C++11 Standard, how do I prove that the snippet below doesn’t compile?
  2. What are the rules about using an underscore in a C++ identifier?
  3. Why aren’t variable-length arrays part of the C++ standard?
  4. Where do I find the current C or C++ standard documents?
  5. What are the new features in C++17?
  6. What’s the difference between __PRETTY_FUNCTION__, __FUNCTION__, __func__?
  7. Where exactly does C++ standard say dereferencing an uninitialized pointer is undefined behavior?
  8. A most vexing parse error: constructor with no arguments
  9. C++ Static member method call on class instance
  10. Why do const references extend the lifetime of rvalues?
  11. Computing length of a C string at compile time. Is this really a constexpr?
  12. Is there a way to access the underlying container of STL container adaptors?
  13. Is right shift undefined behavior if the count is larger than the width of the type?
  14. Is the order of iterating through std::map known (and guaranteed by the standard)?
  15. std::vector and contiguous memory of multidimensional arrays
  16. Why an unnamed namespace is a “superior” alternative to static? [duplicate]
  17. When can you omit the file extension in an #include directive?
  18. Defining a variable in the condition part of an if-statement?
  19. Base pointer to array of derived objects
  20. Why statements cannot appear at namespace scope?
  21. C++ Modules – why were they removed from C++0x? Will they be back later on?
  22. Standard Library Containers with additional optional template parameters?
  23. Is it unspecified behavior to compare pointers to different arrays for equality?
  24. Is auto_ptr deprecated?
  25. Can I legally reinterpret_cast between layout-compatible standard-layout types?
  26. ISO C++ standard draft
  27. Does the C++ standard specify anything on the representation of floating point numbers?
  28. Why must a std::ranges::filter_view object be non-const for querying its elements?
  29. Do pointers to string literals remain valid after a function returns?
  30. is size_t always unsigned?

Leave a Comment