 | | Re: NQC 2.1 b2 in beta test
|
| (...) I think NQC should be strictly a compiler. It seems like it would be more manageable for both developers and users if the RCX communication pieces were in a separate executable. This change should make NQC completely portable (if there is such (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
| | | | | Re: NQC 2.1 b2 in beta test
|
| (...) If this is done, the compiler should have an option to spit out compiled bytecode on stdout, and the rcxcomm program should have a matching option to accept bytecodes on stdin and send them to the rcx. And then there should be a wrapper that (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
| |
