> So
>if (a = a + 1024)
>
> evaluates a + 1024, then assigns the result to a, then tests the result
> (of the new a) for true or false ... (or zero or non zero) so it'll always
> be true...
In the interest of nitpicking: if a has value of 64512 then this evaluates
to 0 ie false. Seeing that '
Gordon Henderson wrote:
> That's not what that statement is doing.
>
> One = is an assignment, 2 == is comparision.
>
> So
>if (a = a + 1024)
>
> evaluates a + 1024, then assigns the result to a, then tests the result
> (of the new a) for true or false ... (or zero or non zero) so it'll al
On Wed, 6 Jan 2010, Sean Cross wrote:
> First off, Sorry for the new thread, my old free email account was
> bouncing your replies, and by chance i saw your replies through the
> archived lists.
> I have since changed e-mail accounts, so there should not be any more of
> a bounce problem. (i hope)
First off, Sorry for the new thread, my old free email account was
bouncing your replies, and by chance i saw your replies through the
archived lists.
I have since changed e-mail accounts, so there should not be any more of
a bounce problem. (i hope)
using sdcc 2.9.0 and mcu8051ide for simulato
