> The scenario in which you inadvertently use a "skip" instruction
> of some kind, 'around' a macro instance that generates multiple
> instructions

Good point. I hinted at that by saying "(3) no or less time spent
debugging sections that are done deals (IF you have been careful)"

However, there are so many things that can go wrong when coding.
If one doesn't get you, another will. And it's always our own fault. The
PIC only does what it's told to

Skips are probably the most obvious to watch for, and GOTO $x
too. Not such a good idea for portability into or out of the 18 series
(because of the two-word architecture) either, although I am guilty
of doing it. But generally only on projects that were designed for a
particular PIC and will more than likely stay in that PIC. Skips and
jumps should be made to labels, tidier

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics