I stand corrected.  I was looking at rev D, they decided to cave and
     put them back in rev E. But my main caution about knowing what they
     REALLY do stands.  Take for example:

     Psuedo OP:         Compiles to:
     ADDCF f,d          BTFSC 3,0
                        INCF  f,d

     In this case two instructions are compiled for one pseudo-op.  Again,
     using only the native instructions is the safest course.

     Scott


______________________________ Reply Separator _________________________________
Subject: Re[3]: reference card
Author:  Craig Knotts <Craig.Knotts@CCMAIL.CARRIER.UTC.COM> at Internet_Exchange
Date:    2/19/97 2:56 PM


     Considering the latest MPASM manual (release E) includes these
     pseudo-ops, it would appear that they ARE documented and officially
     supported.


______________________________ Reply Separator _________________________________
Subject: Re[2]: reference card
Author:  Scott Fink <Scott.Fink@MICROCHIP.COM> at Internet
Date:    2/19/97 12:08 PM


     Brian,

     It is OK to use these "hidden" instructions like skpnz as long as you
     remember that they are actually MPASM pseudo-ops and that some of them
     assemble to multiple op codes (i.e. take more than one instruction
     cycle).  The only "real" instructions are those listed in the
     datasheets.  I have talked to a lot of people who have problems because
     they forget which are op-codes and which are pseudo-ops and their
     timing loops come out wrong ("the PIC must be missing a clock or
     something", wrong, you used a multiple instruction pseudo-op).

     You may also note that they are no longer documented in the MPASM
     users guide and are not therefore officially supported or guaranteed
     to work on future versions.  Use caution when using them.

     Best Regards,
     Scott