A
Andreas Koch
Hi all,
just a weird idea.
I am developing an interpreted language (bytecode
interpreter) for a very limited machine.
Now, i could invent my own bytecode.
Or i could adapt java's bytecode engine.
I don't know very much about java bytecode yet;
Just that it is 32-bit stack orientated.
Note that the device is too limited to hold
more than an interpreter for an simple bytecode,
plus a minimalistic api (writechar,writeint,
readkey etc). It couldn't handle the class
libraries, not even the J2ME ones.
So
1) Can the java bytecode machine be separated
from the classes and other dependencies
(garbage collector?) so it can serve as "just an
intepreted stack based assembly language"
2) If this can be done, can the usual java
tools (read: java compilers, debuggers, etc) be used
to write code for this machine ?
just a weird idea.
I am developing an interpreted language (bytecode
interpreter) for a very limited machine.
Now, i could invent my own bytecode.
Or i could adapt java's bytecode engine.
I don't know very much about java bytecode yet;
Just that it is 32-bit stack orientated.
Note that the device is too limited to hold
more than an interpreter for an simple bytecode,
plus a minimalistic api (writechar,writeint,
readkey etc). It couldn't handle the class
libraries, not even the J2ME ones.
So
1) Can the java bytecode machine be separated
from the classes and other dependencies
(garbage collector?) so it can serve as "just an
intepreted stack based assembly language"
2) If this can be done, can the usual java
tools (read: java compilers, debuggers, etc) be used
to write code for this machine ?