Am 22.11.2014 11:39, schrieb Love Nystrom:

On 2014-11-21 04.00, Timo Kreuzer wrote:

Am 20.11.2014 14:18, schrieb Love Nystrom:

Well... Actually not exactly the same.. ;)
"if (f != FALSE)" requires an explicit comparison with a second operand,

No, it does not. It requries the compiler to generate code that executes the following statement, when f is not 0.

I suspect we look at it from two different viewpoints here..
Yours is "C centric" and mine is "object code centric".
You talk about what the compiler is required to do,
and I talk about what comes out at the end of compilation.

And what comes out at the end of the compilation is what the compiler creates. And the compiler is following the rules of the C standard and the rules of logic.
You claimed '"if (f != FALSE)" requires an explicit comparison with a second operand,' and that is factually wrong. No matter whether you are looking at it from the compiler perspective or from the perspective of an expressionist painter living in a yellow tree house on the bottom of Lake Tanganyika.

And.. dear friend.. don't turn this into a pissing contest.

Don't even get me started. I battled the grand master and I survived.

Let's check the egos in with the coat check girl at the entrance.
May I ask how old you are?

Are we talking about age or maturity?

We better end this discussion, it's not leading anywhere. And you don't want me to turn into the Grinch and steal your Christmas.

Thanks,
Timo