 | | Re: NQC 2.1 b3 released
|
|
Will this ver. support the Scout ? Fully? thanks. -Mike (25 years ago, 25-Jan-00, to lugnet.robotics.rcx.nqc, lugnet.robotics)
|
| |
| | Re: identifiers in NQC
|
|
(...) There isn't any practical limit - symbol storage is allocated dynamically and the lexer grows its buffer as needed, so identifiers may be as long as you want (until you run out of memory) and every character is significant. This isn't the most (...) (25 years ago, 25-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.1 b3 released
|
|
Linux builds of NQC are now available in tar.gz and RPM format at: <URL://www.mattdm.or...orms/nqc/> including the new 2.1.b3, as well as the stable 2.0.2 release and some docs packaged nicely. To the best of my knowledge, these binaries work (...) (25 years ago, 25-Jan-00, to lugnet.announce, lugnet.robotics, lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.1 b3 released
|
|
(...) Works great with RcxCC now! Uwe (25 years ago, 24-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | identifiers in NQC
|
|
Usually there is some compiler rule that states: identifiers must be unique within the first _____ characters. That is, long variable and other identifier names may be allowed to be quite long, but they must be unique somewhere in the first X number (...) (25 years ago, 24-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.1 b3 released
|
|
Will try to have linux builds/rpms up at <URL://www.mattdm.or...torms/nqc> (I'm considering setting up nqc.mattdm.org as a more easy-to-remember URL...) within the next few days. Would be right away, but I'm on vacation and away from good net (...) (25 years ago, 24-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC 2.1 b3 released
|
|
No new features - just a few fixes and tweaks: * output files now default to current directory rather than next to source * fixed the __SCOUT bug * fixed the RcxCC problem - two part solution: 1) trailing directory delimiters are now optional on -I (...) (25 years ago, 24-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Help with rotation sensors
|
|
(...) You could probably change the first line to while (SENSOR_1 < target_distance) and it should work fine. Since you want to keep the two rotation sensor values (and hence the two wheel distances) equal, each sensor will individually measure the (...) (25 years ago, 24-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Help with rotation sensors
|
|
Hi all, I'm new to programing so this may seem like a silly question. I'm using two rotation sensors with the program below to eliminate drift caused by different motor speeds. Is it possible to break this loop when a certain distance is reached? I (...) (25 years ago, 23-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.1 b2 in beta test
|
|
(...) Its actually an unfortunate side effect of an upgrade to my compiler...for a more detailed explanation see the tread starting here: (URL) Baum (25 years ago, 21-Jan-00, to lugnet.robotics.rcx.nqc)
|
