Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalBecause the math works.
FALSE OR TRUE is TRUE, because 0 | 1 is 1. ... insert many other examples here. Traditionally, C programs have conditions like
if (someFunctionReturningANumber()) if (someFunctionReturningANumber()) rather than
if (someFunctionReturningANumber() != 0) if (someFunctionReturningANumber() != 0) because the concept of zero being equivalent to false is well-understood.
Because the math works.
FALSE OR TRUE is TRUE, because 0 | 1 is 1. ... insert many other examples here. Traditionally, C programs have conditions like
if (someFunctionReturningANumber()) rather than
if (someFunctionReturningANumber() != 0) because the concept of zero being equivalent to false is well-understood.
Because the math works.
FALSE OR TRUE is TRUE, because 0 | 1 is 1. ... insert many other examples here. Traditionally, C programs have conditions like
if (someFunctionReturningANumber()) rather than
if (someFunctionReturningANumber() != 0) because the concept of zero being equivalent to false is well-understood.
Because the math works.
FALSE ANDOR TRUE is TRUE, because 0 &| 1 is 1. ... insert many other examples here. Traditionally, C programs have conditions like
if (someFunctionReturningANumber()) rather than
if (someFunctionReturningANumber() != 0) because the concept of zero being equivalent to false is well-understood.
Because the math works.
FALSE AND TRUE is TRUE, because 0 & 1 is 1. ... insert many other examples here. Traditionally, C programs have conditions like
if (someFunctionReturningANumber()) rather than
if (someFunctionReturningANumber() != 0) because the concept of zero being equivalent to false is well-understood.
Because the math works.
FALSE OR TRUE is TRUE, because 0 | 1 is 1. ... insert many other examples here. Traditionally, C programs have conditions like
if (someFunctionReturningANumber()) rather than
if (someFunctionReturningANumber() != 0) because the concept of zero being equivalent to false is well-understood.
Because the math works.
FALSE AND TRUE is TRUE, because 0 & 1 is 1. ... insert many other examples here. Traditionally, C programs have conditions like
if (someFunctionReturningANumber()) rather than
if (someFunctionReturningANumber() != 0) because the concept of zero being equivalent to false is well-understood.