 | | Re: LEGO light sensor schematic
|
|
Dennis Clark wrote in message ... (...) Your right. It just can't be the way it is drawn. I think it must be a photo transistor. Usually photo diodes are not as sensitive as photo transistors either. I'll touch up the circuit and see if it looks (...) (28 years ago, 4-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)
|
| |
 | | 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)
|
| |
 | | 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: 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)
|
| |
 | | 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...
|
|
(...) 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...
|
|
(...) 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...
|
|
(...) 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...
|
|
(...) 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)
|