Subject:
|
Re: Alternatives for NQC Event Support
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Tue, 2 May 2000 00:03:20 GMT
|
Reply-To:
|
mattdm@mattdm.NOSPAMorg
|
Viewed:
|
1622 times
|
| |
|
|
Dave Baum <dbaum@spambgoneenteract.com> wrote:
> 3) monitor/catch. Nice structure, but adds new keywords.
> My personal preference is 3. What do other people think? Any other
I like 3, given the +xx problem with try/catch.
--
Matthew Miller ---> mattdm@mattdm.org
Quotes 'R' Us ---> http://quotes-r-us.org/
Boston University Linux ---> http://linux.bu.edu/
|
|
Message is in Reply To:
 | | Alternatives for NQC Event Support
|
| RCX 2.0 adds firmware support for events and resource acquisitiion. The primitives are rather straight-forward. For events, one command beings event monitoring on a set of events, another stops monitoring. If a monitored event occurs, control is (...) (24 years ago, 1-May-00, to lugnet.robotics.rcx.nqc)
|
8 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
