|
|
 | | Re: C$ - Code Only
|
| (...) 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. (...) (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | Re: Elevations for Train 6
|
| (...) Is there also a latest rendition of the overall layout? Jeff gave me a sheet at dinner last month but a) din't have it still, and b) has it changed? Are we still doing the 'perimeter modules' encompassing a seating area? The show organizers (...) (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto)
| | | | | Re: C$ - Code Only
|
| (...) 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 (...) (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | Re: C$ - Code Only
|
| (...) Steve, One of the thing I noticed when working on the book generation code, there are typically multiple unique drop sequences that get you to the same board state, even when just picking the best hypothetical moves. In an RCX environment that (...) (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto)
| | | | | Re: C$ - Code Only
|
| (...) Steve, One of the thing I noticed when working on the book generation code, there are typically multiple unique drop sequences that get you to the same board state, even when just picking the best hypothetical moves. In an RCX environment that (...) (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto)
|
|
