|
|
 | | Question about NQC code
|
| Hi, I created the following light searching program: #define speed 2 #define inaccuracy 2 int lightstrength, max, min; task main() { SetSensor(SENSOR_2,S...OR_LIGHT); start searchforlight_a; } task searchforlight_a() { lightstrength = (...) (23 years ago, 15-Jan-02, to lugnet.robotics.rcx.nqc)
| | | | | Re: BricxCC
|
| (...) that's a good point, especially for larger programs ! Stef Mientki (23 years ago, 15-Jan-02, to lugnet.robotics.rcx.nqc)
| | | | | Re: Some remarks / questions about Brixcc
|
| (...) Sorry about the mixup. I thought I'd tried capturing non-compiler errors with a redirect and it hadn't worked. But trying it just now it definitely does work. BricxCC is already capturing the compiler errors via the -E option. I am trying to (...) (23 years ago, 15-Jan-02, to lugnet.robotics.rcx.nqc)
| | | | | BricxCC
|
| Hi John, I just got a new computer and tested your program on a AMD 1.333GHz Athon (Thunderbird). It works just great! I thank you for the adjustments/adds in your program as I requested. There is just one question left. Since I use to Delphi, I (...) (23 years ago, 15-Jan-02, to lugnet.robotics.rcx.nqc)
| | | | | Re: Some remarks / questions about Brixcc
|
| (...) Error messages go to one of two places. Errors from the compiler default to stderr but can be redirected with the -E option (-Efoo would sent them to a file named "foo"). Other errors (problem communicating with the RCX, illegal command line, (...) (23 years ago, 15-Jan-02, to lugnet.robotics.rcx.nqc)
|
|
