Re: [Oopic-compiler-devel] Reverse-engineering the OOpicMK compiler--preliminary
Status: Planning
Brought to you by:
ndurant
From: Andrew P. <wa...@ic...> - 2004-04-30 01:20:19
|
At 12:18 AM 4/29/2004 -0400, D. Daniel McGlothin wrote: >The OOpic internally is just stack processor, and it seems that all objects, >variables, and results of scripting is just streamed onto the stack, and the >execution pops the byte-code and its arguments, runs the firmware bit >related to the byte-code, and then pushes a result back to the stack. > >But you probably already knew that. Yup. >> I wonder if the codes are identical across all target hardware types. > >It seems so. The differences in hardware seem to be additional >byte-codes/firmware capability as the OOpic revision 'increases'. So it's easy then. Is it done yet? :) ...Andy |