On Sat, Feb 19, 2005 at 08:27:34PM +0100, Wouter van Ooijen wrote:
> > No reason. I took care of that by integrating a gettoken function in
> > the interpreter.
> 
> Now can I write, in your language, in a single program, both the code to
> accesses the external storage device, and the code that is to be
> translated to be P-code? And what does the output look like, one hex
> file for the pic and another one for the external storage device?

I rethought what you wrote Wouter. By two hex files were you implying
that the compiler should produce P-code in one, and an augmented interpreter
in the other?

There's also a third possibly between the true compiler and true interpreter:
having the compiler produce threaded code. NPCI doesn't do that at this time,
and I have no idea where it would fall in the performance/size spectrum between
pure compiled and pure interpreted. But it would completely ditch the
fetch/decode part of the interpretation process. Of course that threaded code
would have to be integrated with the interpreter.

It's an interesting question.

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