> > First, DOCUMENT YOUR CODE!!!  If you had forced yourself to explain what
> > each instruction was doing, you might have found the bug yourself.
>
>     :) I agree with you. But this is documented on the starting of the
file.

That's no excuse.  Yes, header comments are good, but individual details
must be documented too.

>     This is the reason why this code is documented on the starting of the
> file with a big WARNING! I'm using PCH (by CCS) and haven't found a way to
> derive the PCLATH value simbolically.

I thought CCS was a C compiler, but the code you showed was in assembler.

>     This is a good idea. I don't think this code will ever be implemented
on
> more powerfull machines,

Yeah, right.  That's probably what the original author who wrote the 16F877
code thought too.

> but better be safe than sorry. :)

Yes.


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

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body