 | | RE: Something else is needed, I think...
|
|
Maybe we could write a program that compiles c source code into forth :) just joking Joel Shafer joel@connect.net -- Did you check the web site first?: (URL) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) Thank you. Kekoa. I was starting to think I was completely alone in my attitudes. Just a couple of comments on what I think a new byte code should do or be 1) It should resemble machine language. The commands in the bytecode should be (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I don't deny that these are reasonable things to want. But you don't need the JVM to get these. The problem with the JVM is that there is so much extra fluff associated with Java. You mentioned 64-bit floats and ints, security, etc. Why start (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) Basically what you are talking about at this level is an interpreted machine language. The only benefit you get from interpreting it rather than running directly on the hardware is that you can catch errors. However, if the bytecodes are (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) All I am saying is that there will be no existing product that does exactly what everyone wants. However, I think it is worth considering JVM as a starting point close to what we want since it represents a huge body of solid code. (...) (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I don't think I am underestimating the amount of work, actually.Just because a language has a GUI toolkit does NOT make it user friendly or portable. (...) Then it's not self contained on TWO counts. One, as you mentioned, you need NQC to get (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) Yes. (...) Wrong. Because we could design the instruction set from scratch ourselves, a small set of instructions could be included in the entire instruction set which do things require a great deal of regular machine instructions to do. (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) Q: How large are the compiled FP emulation routines for the RCX? -Kekoa (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | RE: Something else is needed, I think...
|
|
Kekoa wrote: <actually he wrote stuff here that I snipped out> (...) Ah, a refreshing viewpoint :-) Getting concrete ideas and proposals out makes sense. If you don't have the time to propose a CONCRETE idea or plan, then you sure don't have time to (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) Well, having a bytecode for turning on a motor seems little benefit compared to calling a library function to do it. From the user's point of view, the effort and the result are similar. (...) Actually, you need to have a call stack and a (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) Maybe the JVM is, in spirit, close to what we want; but can you honestly say that porting the JVM to the RCX will be easier than writing something from scratch, perhaps using some of the better features of the JVM as inspiration? I personally (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) Total .text section is 5832 bytes, .rodata is 4 bytes, and .bss is 8 bytes. This is for all for all of the FP emulation routines, only those actually used will be linked in. This is only the helper routines, not anything from the math library. (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) Sorry to step in here. But there is no difference (as I see it) between having a system library function that runs the motors and having a byte code that runs the motors. It's all a matter of encoding. If I say: set_motor_speed(MOTOR1, 20); (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) This is good to know, I now know that any byte code interpreter that uses floating point will have to devote on the order of (at least) 6K to floating point if it wants to support floating point. Considering that any interpreter that uses the (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I guess it depends on what you want in your firmware. I have been working on my own object-oriented kernel, and I have written an object-oriented kernel for an embedded I/O controller before, and it is a big job. That is just the OS, not (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | 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)
|