 | | Re: Some comments (long)
|
|
(...) Could you explain what you mean by this, exactly? I would have figured that if a new interpreter is designed from scratch, the lengths of the opcodes could be hard-coded into the interpreter in some way. I was not suggesting that any existing (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: Some comments (long) (was: Something else is needed, I think...)
|
|
Mark Tarrabain wrote in message <3730DE97.EFB3BF9A@l....bc.ca>... (...) It is probably true that a floating-point library cannot (should not?) be built into the firmware. It would probably be better for this to be supported by the compiler(s). But (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: LEGO light sensor schematic
|
|
(...) Sorry about that, I glued it back together with liquid plastic cement. I don't think it can take another operation and survive. I can't remember seeing a number inside and I was looking in there when you wedge the pc board in place. You might (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: Lego Network Protocol questions
|
|
(...) I was under the impression you wanted to sync a clock to the rhythm of bit arrivals. You cannot do this. You can definitely sync a clock to the rhythm of byte arrivals. I was trying to point out this distinction to you. You must have been (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: Some comments (long)
|
|
(...) Unfortunately, the ROM code (as I understand it) does not implement any mechanism other than polling. I would like to do things like block a thread until a sensor value matched some criteria. The only efficient way to do that is to have the (...) (28 years ago, 6-May-99, to lugnet.robotics)
|