 | | 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)
|
