> I like these 3 home made mnemonics;
> #define         skp1    goto $+1+1      ; skips one instruction
> #define         skp2    goto $+1+2      ; skips 2 instructions
> #define         skp3    goto $+1+3      ; skips 3 instructions
> (never needed skp4)
>
> These can really neaten-up code and avoid the use
> of messy un-needed goto labels when all you want
> to do is skip the next 3 instructions;
>
>         btfss input,2           ; test input
>         skp3                    ;
>         movlw b'11001100'       ; input == hi, so do these 3
>         movwf lastb             ;
>         movwf PORTB             ;

I can agree with this up to a point.  The longer the skip, the greater the
chance that someone won't notice it when editing the code.  At the least,
skips longer than 1 instruction should be clearly documented at the
skipped-to point.


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

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu