 | | 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
|
|
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
|
|
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
|
|
It works fine in 2.1, as promised. Thanks Dave! -- Mark Haye, haye (at) us (dot) ibm (dot) com IBM TSM Server Development, Tucson, AZ Dave Baum <dbaum@spambgoneenteract.com> wrote in message news:dbaum-1DBD80.21...net.com... (...) ... (25 years ago, 24-Feb-00, to lugnet.robotics.rcx.nqc)
|
