 | | Re: NQC versus Lego RCX Code Speed —Steve Baker
|
| | | (...) As I understand it, the situation is this: * Using the Windoze graphical environment - your 'programs' are translated into a special 'byte-code' that's interpreted by the RCX's firmware. * Using NQC, your C programs are translated into the (...) (24 years ago, 6-Oct-00, to lugnet.robotics)
|
| | | |
| | | | | Re: NQC versus Lego RCX Code Speed —Luis Villa
|
| | | | (...) This is correct. (...) Hehe :) Yes, this is correct. LegOS is also faster for some other reasons- it samples the sensors at a much faster rate than the standard firmware, so legOS programs can react much more quickly than standard bytecode (...) (24 years ago, 6-Oct-00, to lugnet.robotics)
|
| | | | |
| | | | | | RE: NQC versus Lego RCX Code Speed —Ralph Hempel
|
| | | | (...) (URL) Is a note I posted a while back on pbForth speed. It really is very fast - not as quick as legOS, but fast enough for what we're doing. In fact, NQC and native firmware is fast enough - we just don't have enough variables.... As a point (...) (24 years ago, 6-Oct-00, to lugnet.robotics)
|
| | | | |
