Re: equality operator question

Krice <paulkp@[EMAIL PROTECTED]
> writes:

> On 5 touko, 16:19, James Kanze <james.ka...@[EMAIL PROTECTED]
> wrote:
>> First of all, you never compare with true or false.
>
> I'm doing that. What could go wrong?

Well, with false, not much wrong, since false must be == !true, and
if(false){this;}else{that;} must evaluate that, we're about certain
that false == 0.

But for true, it's something else.  It may be 1, -1, 0xff, or whatever
not 0.

But in any case, it's harder to read boolean expression when you add
equivalences with the constants.

Compare:
 

   Is it true that it is false that you're not big?   
   if(true==(false==(not(you->big())))){ fast();}

   Are you big?                                       
   if(you->big()){                       fast();}
   

Ok, even if you remove some == and some not, it's still harder to
understand the question:

   Is it true that you're big?
   if(true==you->big()){                 fast();}



-- 
__Pascal Bourguignon__