 | | Re: Something else is needed, I think...
|
| (...) That was my point, that it was not a benefit for having an interpreted "machine language" over using native machine language. The only benefits are portability and error checking, and the error checking is problematic when you get to that low (...) (28 years ago, 3-May-99, to lugnet.robotics)
| | |  | | Re: Something else is needed, I think...
|
| (...) So this is a nice start at least. Regarding things you like, I'm going to ignore 1) and 6) because they are not features of byte code, they are features of Java; you either use the JVM and you get them, or you do not use the JVM and you do not (...) (28 years ago, 3-May-99, to lugnet.robotics)
| | |  | | FW: Something else is needed, I think...
|
| -----Original Message----- From: Ralph Hempel [mailto:rhempel@bmts.com] Sent: Monday, May 03, 1999 7:07 PM To: Mark Tarrabain Subject: RE: Something else is needed, I think... (...) The FORTH bytecode producer is an UMBILICAL forth, and then you (...) (28 years ago, 3-May-99, to lugnet.robotics)
| | |  | | Re: FW: Something else is needed, I think...
|
| (...) The problem is he doesn't understand how forth works (no offense intended). Basically, all you save is the actual parser -- there is no "compiler". A typical forth implementation (and I have no idea if this relates to pbForth at all) (...) (28 years ago, 3-May-99, to lugnet.robotics)
| | |  | | Re: Something else is needed, I think...
|
| (...) For reference, the JVM specification is available online at this URL: (URL) are several features that promote compactness: 1) it is a stack-based bytecode. Operands are pushed onto the stack, a bytecode is executed, and results are pushed onto (...) (28 years ago, 4-May-99, to lugnet.robotics)
| |