 | | Re: RCX and Java
|
| (...) I don't think anyone is suggesting that Java is appropriate for a hard-realtime system. Personally, I would expect nothing less than an RTOS with a deadline-based scheduler and a low-level language. However, I think the RCX does not have any (...) (28 years ago, 5-May-99, to lugnet.robotics)
| | |  | | Re: FW: Something else is needed, I think...
|
| (...) The one advantage to working with radix 10, on the RCX at least, is that the display routines use this radix, so even if you prefer working with some power of two radix, you might find yourself stuck converting in the end. Not that this is (...) (28 years ago, 5-May-99, to lugnet.robotics)
| | |  | | Re: FW: Something else is needed, I think...
|
| (...) This is a possibility I had not thought of, also worth thinking about more. It certainly complicates the compiler writer's job, but aside from that it sounds like a reasonable of doing things. -Kekoa (28 years ago, 5-May-99, to lugnet.robotics)
| | |  | | Re: FW: Something else is needed, I think...
|
| (...) I see what you like about having a FixedPoint type and being able to say a = b.Multiply(c) This gives you the flexibility to add modules as you need them by dumping all the work onto the compiler, which is not a bad place if you are not the (...) (28 years ago, 5-May-99, to lugnet.robotics)
| | |  | | Re: FW: Something else is needed, I think...
|
| (...) That's true. My very first fixed point implementation was in radix 10. At the time I didn't even know what I was doing was called fix point. Later, in graphics work, it just seemed obvious to use radix 2 since there are several tricks that (...) (28 years ago, 5-May-99, to lugnet.robotics)
| |