> Perhaps it would be better to deffine two macros, the normal version
> and the "skipable" version, that starts with your branches and then
> inludes the normal deffinition. That way, you don't loose speed
> when you don't need it.

You could take this another step farther and make a SKIPPABLE macro:


skippable macro target
     local   skipover, doit
     bra     doit
     bra     skipover
doit
     target
skipover
     endm


This marcro would be used as:


     btfsc   flag_afu  ;everything still OK?
     skippable reset_everything ;no, reset everything


Note that this is completely untested and I'm not totally confident it
will work.

In reality, this situation doesn't seem to come up very often.  I've done
lots of PIC projects, and I don't remember ever wishing there was a
solution for this.


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

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.