2007/5/14, Jinx wrote:
> The quickest (and probably most efficient and character-building) thing
> you could do would be to go through the code very carefully line by line,
> assuming nothing, and comment and explain to yourself every instruction
> and its effect/consequences. When checking your own code for bugs
> you have to be very disciplined. That's why buggy code presented to the
> list is usually sorted pretty quickly. An error is often more easily spotted
> by someone else. It is just too easy to miss errors, like a MOVFW
> instead of MOVWF, if you assume and skim

... and check the silicon errata sheet, to make sure that the chip at
your hand would actually work as documented in the data sheet :)


Best regards,

-- 
WH Tan
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist