On Wed, 2005-06-29 at 17:52 +0200, Jan-Erik Soderholm wrote:

> I guess that what it realy does, is to jump to
> its own "end", and that the PIC then just
> "falls through" to the next 
> ISR, becuse they
> happens to be stuffed together physicaly in
> memory, 
> right ?

Yes 100% correct.

> And each handler doesn't realy knows about
> the others, do they 

No, no connection between them.

> Are you takling about *pre-assembled* library ?
> (Either as .O 
> files or as a .LIB) ?

Yes.  I guess my "big computer" mentality is showing here.  I'm used to
putting all my useful bits of C code into libraries for later reuse.

> It seems as pre-assembled code isn't used
> very 
> much with the PICs, mainly becuse you
> miss all assembly time 
> calculations and
> conditional assembly that can make the
> "library 
> routines" realy flexible. Most seems
> to keep theirs "code libs" as 
> source code...

There's no reason why a single source file with conditional assembly
can't still be used to produce libraries.  I'm planning to use
subdirectories to hold the .o and .a files for the various target PICs
and to use "make" to rebuild for only the required target when the
sources change.

I'll write it up when I've got it working.

Peter



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