Logical AND, OR: Is left-to-right evaluation guaranteed?

by

Yes, it’s guaranteed, otherwise such operators would lose much of their usefulness.

Important notice: this is valid only for the builtin && and ||; if some criminal overloads them, they are treated as “regular” overloaded binary operators, so in this case both operands are always evaluated, and in unspecified order as usual. For this reason, never overload them – it breaks a hugely important assumption about the control flow of the program.

Relevant standard quotations

Builtin && and || have guaranteed short-circuit behavior

§5.14 ¶1

Unlike &, && guarantees left-to-right evaluation: the second operand is not evaluated if the first operand is false.

§5.15 ¶1

Unlike |, || guarantees left-to-right evaluation; moreover, the second operand is not evaluated if the first operand evaluates to true.

If overloaded, they behave as “regular” binary operators (no short-circuit or guaranteed ordering of evaluation)

§13.5 ¶9

Operators not mentioned explicitly in subclauses 13.5.3 through 13.5.7 act as ordinary unary and binary operators obeying the rules of 13.5.1 or 13.5.2.

and && and || are not mentioned explicitly in these subclauses, so regular §13.5.2 holds:

§13.5.2 ¶1

A binary operator shall be implemented either by a non-static member function (9.3) with one parameter or by a non-member function with two parameters. Thus, for any binary operator @, x@y can be interpreted
as either x.operator@(y) or operator@(x,y).

with no special provision for evaluating only one side or in a particular order.

(all quotations from the C++11 standard)

More Related Contents:

  1. Is short-circuiting logical operators mandated? And evaluation order?
  2. What are the evaluation order guarantees introduced by C++17?
  3. Compilers and argument order of evaluation in C++
  4. Is (4 > y > 1) a valid statement in C++? How do you evaluate it if so?
  5. Post-increment and pre-increment within a ‘for’ loop produce same output [duplicate]
  6. Operator Precedence vs Order of Evaluation
  7. Enforcing statement order in C++
  8. The written versions of the logical operators
  9. order of evaluation of operands
  10. Unexpected order of evaluation (compiler bug?) [duplicate]
  11. Order of evaluation of elements in list-initialization
  12. Order of evaluation of assignment statement in C++
  13. Multiple preincrement operations on a variable in C++(C ?)
  14. Order of execution in constructor initialization list
  15. How do we explain the result of the expression (++x)+(++x)+(++x)?
  16. Logical XOR operator in C++?
  17. Is there actually a reason why overloaded && and || don’t short circuit?
  18. “IF” argument evaluation order?
  19. Why does the expression a = a + b – ( b = a ) give a sequence point warning in c++?
  20. Ternary conditional and assignment operator precedence
  21. Does this code from “The C++ Programming Language” 4th edition section 36.3.6 have well-defined behavior?
  22. What’s the precedence of comma operator inside conditional operator in C++?
  23. Who defines C operator precedence and associativity?
  24. The output of cout
  25. How is “std::cin>>value” evaluated in a while loop?
  26. order of evaluation of function parameters
  27. What is the meaning of “res” in C++?
  28. no default constructor exists for class
  29. DSO missing from command line [duplicate]
  30. How to set Visual Studio Filters for nested sub directory using cmake

Leave a Comment