 | | Re: size of programs
|
|
Not at all, that would be EXTREMELY handy. Something for this release? or later down the road? (...) (25 years ago, 15-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: size of programs
|
|
(...) As mentioned in another post you can add up the sizes of each task/sub in the listing. I know this is tedious. I was considering adding a diagnostic message after download that would show the total number of bytes downloaded. Anyone have (...) (25 years ago, 15-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: size of programs
|
|
If you use RcxCC, look at the code listing. At the bottom of each task you will find the address of the last OP code. Just total them up and you have the size. If you don't have RcxCC, just use the -L option to generate the code listing. --- DonC (...) (25 years ago, 14-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | size of programs
|
|
Hi Is there an easy way of calculating the exact size of a program in bytes (for NQC). I would like to know how much I've got available for the datalog when the program is downloaded. The "dots" in the download-process, do they signify anything, or (...) (25 years ago, 14-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Having trouble with -D option
|
|
One other thing ... when I first made a simple program to demonstrate the problem, I used a lowercase d for my symbol and got this error: # Error: parse error File "rcx.nqh" ; line 118 # void SetDirection(const int o, const int d) { asm { 0xe1, (o) (...) (25 years ago, 12-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Having trouble with -D option
|
|
Thanks for the quick response. "It's fixed in the next release, which is due in a week or so" qualifies for excellent support, IMHO. :) My workaround is a REXX exec rewritting a small header file on the fly before each compile. -- Mark Haye, haye (...) (25 years ago, 12-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Having trouble with -D option
|
|
Yes, I noticed that too, but I'm trying to program multiple RCXs with the same source, and the symbol is meant to represent the RCX's id, so it must have multiple values. Thanks anyway for the quick response. -- Mark Haye, haye (at) us (dot) ibm (...) (25 years ago, 12-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: scout.nqh no longer necessary?
|
|
(...) Correct. Initially (2.1 b1) I put the Scout support in a separate include file because I wasn't ready to merge all of the changes together. As of b2, the compiler's built-in system include file includes RCX, Cybermaster, and Scout APIs. Dave (25 years ago, 12-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: scout.nqh no longer necessary?
|
|
(...) Yes, this is true as of 2.1.b2. (25 years ago, 11-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | scout.nqh no longer necessary?
|
|
It looks like Scout programs no longer need `#include "scout.nqh"', and the file has been removed from the NQC beta distribution. Is that correct? I've been confusing someone new to NQC because I didn't realize this :( --Ben (25 years ago, 11-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Having trouble with -D option
|
|
You found a bug - NQC is actually defining D to be the tokens =1, which then leads to a lot of confusion later on. Basically I bungled the pointer math. I fixed the source so the next release (2.1 final) should be fine. I'll probably release 2.1 in (...) (25 years ago, 11-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Having trouble with -D option
|
|
(...) Same with 2.1b3. FWIW, #ifdef D task main() {} #endif works as expected. D is getting defined, just not to 1. (Or to any number.) (25 years ago, 11-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Having trouble with -D option
|
|
If I compile this program (named d.nqc): /* nqc program */ #if (D == 1) task main() {} #endif with the command: nqc -DD=1 d.nqc I get the following error: # Error: syntax error in expression File "d.nqc" ; line 2 # #if (D == 1) # ^ #---...--- # 1 (...) (25 years ago, 10-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | nqc.mattdm.org
|
|
I set up (URL) to be the permanent home of the Linux binaries and RPM packages I'm building for Dave. The old URL will still work -- it just gets redirected. (25 years ago, 6-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: lego photo scanner... Quite C?
|
|
(...) Y'know, this is a cute name, but it's kind of confusing! (25 years ago, 5-Feb-00, to lugnet.robotics.rcx.nqc, lugnet.robotics.rcx)
|
| |
| | Re: lego photo scanner... Quite C?
|
|
Are you using Quite C? -- ___...___ Ferrara Francesco Jay <getochkn@home.com> wrote in message news:Fp0z10.D4H@lugnet.com... (...) (25 years ago, 4-Feb-00, to lugnet.robotics.rcx.nqc, lugnet.robotics.rcx)
|
| |
| | Re: Curious problem with download
|
|
(...) NQC will first attempt to 'ping' the RCX, but if this fails I'm pretty sure it will give up completely. However, each command that is sent is retried several times (with increasing timeouts for each try) until an acknowledgement is heard. Its (...) (25 years ago, 4-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | RE: Curious problem with download
|
|
(...) Don't forget that your monitor may also interfere with the download. I've had problems go away when I put the RCX/tower away from the front of my monitor... Cheers, Ralph Hempel - P.Eng ---...--- Check out pbFORTH for LEGO Mindstorms at: (URL) (...) (25 years ago, 3-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Curious problem with download
|
|
(...) Unfortunately, the problem is not ambient light. I was trying this in a dark room at night. The only light source in the room was the monitor. I really think we can rule out the tower since my friends RCX loads with my IR tower just fine, and (...) (25 years ago, 3-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Curious problem with download
|
|
(...) Offhand, I'd suspect that the problem is either interference from lighting in the room, or perhaps your IR tower is 'marginal'. From your tests so far it doesn't sound like the problem follows either a specific computer or an RCX. Minimize the (...) (25 years ago, 2-Feb-00, to lugnet.robotics.rcx.nqc)
|
