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