Philip Pemberton wrote:
> Oh, I do that sort of thing a lot. My debugging sessions usually go something 
> like this:
>    1. Comment out an instruction after a BTFSx, without commenting out the 
> BTFSx itself. For bonus points, make a few more changes at the same time.
>    2. Wonder why the code stopped working
>    3. Scratch head a few times and scan through the code looking for obvious 
> mistakes. Completely miss the BTFSx followed by a comment
>    4. Tear out some hair, read through the code again

Somewhere between steps 2 and 4 is when I ask my version control system 
for a diff between the last checked-in version and the current code. 
This often helps find these kinds of editing errors.

(Of course, this is most useful if you check in your code often.)
-- 
Timothy J. Weber
http://timothyweber.org
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist