From: Dan Doel <djd15@...>
Date: 2003-08-11T08:44:23+09:00
Subject: Re: Ruby and OOP-design (question of an old "procedural person" ;)

Mike Campbell wrote:

>>The big reason for & and && is that && is lazy, while & evaluates all
>>its arguments.
>>    
>>
>
>In what language(s)?  I think that's the case in Java, but not in C/C++ if I
>recall correctly, which I might not.
>
>  
>
I'm pretty sure it's lazy in C++ too.

I'm not sure about C, but I would assume it is, because there's no 
booleans in C so it'd be totally useless
as it would do the exact same thing as &.

|| and | could, theoretically be different if || always gave 1 and | 
gave whatever the bitwise answer is, but
I don't know off hand.

I thought laziness was the big factor in && and ||.

- Dan