 | | Which way is faster?
|
|
I want to know which way is faster: 1. Use three tasks to watch sensors task watch1() { while (true) { if () { .. } } } task watch2() { while (true) { if () { .. } } } task watch3() { while (true) { if () { .. } } } 2. Use one task with multi (...) (23 years ago, 13-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Dynamic lists allowed?
|
|
(...) Thanks for your help. The program is running fine now. Would you happen to know if anyone has created this sort of high level functions? If not more people might be interested. jm (23 years ago, 13-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | New RcxCC revision posted
|
|
Anyone who is interested in trying my revised RcxCC can find a copy at: (URL) just uploaded another revision that implements several new features: 1) command line switches: /? or /help = display a help message on startup before continuing /COM=N = (...) (23 years ago, 12-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Dynamic lists allowed?
|
|
(...) This should be "struct tNode *next;" (...) After this, any time you want to refer to a tNode, you need to say "struct tNode". Or you can put "typedef struct tNode tNode" and then use the "tNode" as a type like you're doing. (23 years ago, 12-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Dynamic lists allowed?
|
|
Since I just got started with legOs (thanks to 'Extreme Mindstorms'), I'm creating a set of high level utility functions. This one here is intended to display a DYNAMIC list of values, but there seems to be a problem with the use of 'struct' and (...) (23 years ago, 12-Apr-01, to lugnet.robotics.rcx.legos)
|
