Olin Lathrop wrote:
>
> > Something nobody mentioned yet is just to put
> > a goto block_end (etc) before the code block you
> > want to disable. This has the added advantage
> > of still assembling ALL the code, so code and
> > tables that cross code pages etc will still remain
> > in the same positions in memory,
>
> Except for the added GOTO.


Well when using this quick-and-nasty technique
I actually comment out the first inst of the block
and use the goto instead. But i'm sure you knew that
already. :o)
-Roman

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads