Question

What’s the reason for the following behavior?

class BoolWrapper
{
public:
    BoolWrapper(bool value) : value(value) {}

    operator bool() const { return value; }
    operator int() const { return (int) value; }

private:
    bool value;
};


BoolWrapper bw(true);

if (bw) { ... }            // invokes operator bool()
if (bw == true) { ... }    // invokes operator int() -- why?

Is this behavior expected? (Using GCC 4.7.2.)

Answer 1

Your expectations are based on your belief that the language already knows how to compare two bool values. In reality it doesn’t, however surprising it might sound. More precisely, the language “does not know” how to do it directly.

At the conceptual level, C++ does not have a dedicated built-in equality comparison operator for bool vs. bool comparisons. Even when you write true == false in your code, it is really interpreted by the language as (int) true == (int) false. The implicit conversion to int is introduced by the rules of usual arithmetic conversions and int vs. int comparison is used afterwards.

The most immediate built-in operator that can compare two bool values is the one for int vs. int comparison. This is the operator the compiler is trying to use in your case as well. The very same operator will be used for char vs. char and short vs. short comparisons.

In other words, the only way the compiler can use your bool conversion operator in the bw == true expression would be to do

(int)(bool) bw == (int) true

This is certainly less “optimal” than the direct

(int) bw == (int) true

This is the logic that drives the language to select the latter variant.