Subject:
|
RE: Ooops! NXT Software Comparison correction / I2C Messaging Speed
|
Newsgroups:
|
lugnet.robotics.nxt
|
Date:
|
Thu, 6 Sep 2007 12:45:07 GMT
|
Viewed:
|
22643 times
|
| |
|
|
At 01:54 AM 9/6/07, Dick Swan wrote:
> I'm not complaining about the divergences from Steve's pseudo-code in
> the dual task code. It is a reasonable way to cope with the firmware
> limitations and it is something that I hope Steve will allow under his
> rules although there is a good argument otherwise. But I do think it
> is unlikely that this technique will be widely used; at least not
> until code for the second task is automatically generated by the
> compiler / firmware as it already is for ROBOTC and pbLUA.
I want to list both. First, the one-to-one mapping, and second (with
some explanation) the code with a second task. Several other pieces
of software have an "optimized" version of code, and it makes sense
to do the same for NBC.
Steve
|
|
Message is in Reply To:
13 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
Active threads in NXT programmable brick
|
|
|
|
|
|
