 | | NQC on Scout
|
| Okay, I wrote my first (sophomoric) piece of code for the scout, and I have kind of lame question. I know that there's no good way to answer this question, but about how much code can I stuff in the thing? I've heard that it only has 1kbyte for (...) (24 years ago, 8-Nov-00, to lugnet.robotics)
| | | | | Re: NQC on Scout
|
| (...) It has 400bytes (.4k) for code... I got a twenty line NQC program in there... Dean -- Coin-Op's For Sale!: (URL) Lego Workshop: (URL) Lego Club: (URL) (24 years ago, 9-Nov-00, to lugnet.robotics)
| | | | | Re: NQC on Scout
|
| (...) Well, if you run "nqc -Ofilename yourprogram.nqc", you'll save the compiled code to 'filename' - look at the length of that file. I don't think it's exactly the right size because it seems to contain ASCII strings for the names of functions (...) (24 years ago, 9-Nov-00, to lugnet.robotics)
| | | | | Re: NQC on Scout
|
| (...) (24 years ago, 9-Nov-00, to lugnet.robotics)
| | | | | Re: NQC on Scout
|
| (...) Variables don't take up space (unfortunately). They're purely register variables. (24 years ago, 9-Nov-00, to lugnet.robotics)
| | | | | Re: NQC on Scout
|
| (...) Yes, that looks about the size of it... Any bytes left over? (Use the -l option in NQC) -- Coin-Op's For Sale!: (URL) Lego Workshop: (URL) Lego Club: (URL) (24 years ago, 9-Nov-00, to lugnet.robotics)
| | | | | Re: NQC on Scout
|
| (...) That's good. Any less then 400 bytes would truly be daft. The system vars and pointers are already taken from the 1k of RAM. Dean -- Coin-Op's For Sale!: (URL) Lego Workshop: (URL) Lego Club: (URL) (24 years ago, 9-Nov-00, to lugnet.robotics)
| |
