> > I don't have any tutorial, but lots of code template and examples at
> > http://www.embedinc.com/pic.
>
>   Pretty bad Olin. Such a great specialist like you are, may waste 8 hours
> from one weekend to write a trully tutorial. Or at least to document
better the
> examples you have there...

I have other things I'd rather do than write a linker tutorial.  Unless of
course you want to pay me $110/hour, in which case I'd be happy to write
one.  I learned the linker by reading the manual.  It's not that hard and
not that long.  I don't see much point in a document that just repeats what
Microchip says.  I wouldn't have much to add.

However, I do want my examples to be well documented.  It's not the
documentation's job to teach you about PICs, but it should describe what the
examples are doing assuming you already know about PICs and my development
environment in general.  I thought that I did document the code reasonably
well, in my opinion far better than other code I've seen cross the PIClist.
General statements like "pretty bad" and that it should be "documented
better" aren't very useful and I think quite unfair (I don't HAVE to provide
any information for free).  What specifically do you find "pretty bad"?
What documentation exactly is missing from which file?


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

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