Wed Apr 6 21:11:32 EDT 2011

PIC18 extended instruction set

It's a pain in the ass because it forces you to choose.  Damn
premature optimization!

For C it's a no-brainer.  For Staapl PIC18 Forth however, I don't know
whether it's a good idea because it effectively splits the code into
two different platforms.  The "current pointer" is too useful to not

So maybe from an organizational point of view it's best to not use it
at all, then all PIC18 targets can use the same code.

So, to move the USB driver forward: I need a fast implementation of
indirect data access, or a different approach for accessing the
endpoint registers.