> 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?

I was thinking of a PIC plus an external EEPROM. PIC contains PIC code
and maybe P-code, the EEPROM can obviously contain only p-code. How
would you deliver the content of PIC and EEPROM?

> 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.

Threaded code is not a good match for the very small stack of mid-range
PICs.

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu
 

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