> Already know about that. INDF0 Equates to a 12 bit quantity. Using movf
> chops off 4 of the 12 bits in all cases. Say what you want about this,
> it
> does not make sense to take an obvious constant that will not fit in the
> instruction it's used in and accept it without warnings or errors.
> Requiring the user to do something like this:
>
>         movf    (INDF0 & 0xff), W
>
> Should be acceptable, but silent truncation is NEVER a good idea - in
> any language.

Then you'd have cumbersome and ugly syntax on almost every file register
reference.  Yuk.  Since you'd have to AND the address with FFh most of the
time, it might as well be understood that it will always be done
automatically.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body