Barry Gershenfeld escreveu:
>  *fnt =3D *fnt ^ 0xFF;
>
> My approach when the compiler doesn't seem to understand, is to speak lou=
dly
> and slowly...
>
> int y;   // Pronounced, "why?"
>
> y =3D *fnt;
> y =3D y ^ 0xFF;
> *fnt =3D y;
>
> (Also known as, "leave nothing to chance")
>
> It takes me less time to try that, then it does to ask on a list.  If I
> still don't see it, I 'watch' or print the values.  Then I watch it in
> machine code.  I rarely get to that.  Usually it's something stupid I did.
> Occasionally, it's something stupid the compiler did.  Things like,  I
> *thought* the ^ was an xor, but wasn't.  I gotta see proof.
>
> BTW I don't see 'const' being used anywhere, but I thought a const byte *
> meant not that the pointer couldn't change, just the pointer's own address
> didn't.  But see, there's two more questions, (1) to see if I'm right, and
> (2) to see if the compiler got it right :)
>
> Barry
>   =


When 'const' is to the left side of the asterisk, it means that the
element pointed by the pointer must not be changed. When the 'const' is
to the right side of the asterisk, then the pointer value itself must
not be changed.

The pointer own address can't be changed, only its own content (address
of the element pointed by it) or the content of the element pointed by it.

Regards,

Isaac


__________________________________________________
Fa=E7a liga=E7=F5es para outros computadores com o novo Yahoo! Messenger =

http://br.beta.messenger.yahoo.com/ =

-- =

http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist