 | | Re: C$ - Code Only —Larry Pieniazek
| | | | (...) Forgive a clueless question here, but is QuiteC different than NotQuiteC? If so where can I learn more about it? Thanks! The oldest mention of the term "QuiteC" I could find on LUGNET was only 3 weeks ago but MAYBE I'm searching wrong? see (...) (20 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | | | | | | Re: C$ - Code Only —Kevin L. Clague
| | | | | (...) NQC compiles not quite C code into LEGO firmware opcodes. You download the .rcx result, and LEGO firmware interprets the program. This makes it slow. QuiteC and brickOS both use H8 native C compilers that spit out H8 assembly code directly. (...) (20 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | | | | | | | | Re: C$ - Code Only —Joseph Woolley
| | | | | (...) I am admittedly biased toward BrickOS; however, I am wondering if you attempted to free some memory in BrickOS by disabling features that you didn't need? If you are only going to run one program (whether single threaded or multi), you can (...) (20 years ago, 7-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | | | | | | | | Re: C$ - Code Only —Kevin L. Clague
| | | | | (...) Nope. I knew there was a certain amount configurability in brickOS, but I assumed it would be hard to get it down to a minumum. (...) With librcx, I started out with the minimum and added only what I needed. (...) Kevin (20 years ago, 12-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | | |
