To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.nxtOpen lugnet.robotics.nxt in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / NXT / 926
925  |  927
Subject: 
RE: Ooops! NXT Software Comparison correction / I2C Messaging Speed
Newsgroups: 
lugnet.robotics.nxt
Date: 
Thu, 6 Sep 2007 12:45:07 GMT
Viewed: 
22007 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:
  RE: Ooops! NXT Software Comparison correction / I2C Messaging Speed
 
(...) Nobody cheated or is dishonest. Everyone who writes firmware for the NXT is well-intentioned "good" people. Let's not mislabel good modern programming practice -- i.e. hardware device drivers integrated into the low-level firmware -- as (...) (17 years ago, 6-Sep-07, to lugnet.robotics.nxt)

13 Messages in This Thread:





Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR