Subject:
|
Re: What I would do (2)
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Tue, 31 Jan 2006 20:15:36 GMT
|
Viewed:
|
1760 times
|
| |
|
|
> I'm not saying that this will turn out to be the case, but it could. And in the
> unlikely event that it does I am seeking NQC user feedback. Which is more
> important: API compatibility or Performance?
As the brick, sensor, motors... are quite different, direct portability is not
of paramount importance for me. So I vote for performance.
Philo
|
|
Message is in Reply To:
 | | Re: What I would do (2)
|
| (...) I like this concept, but what if in the case of NQC the new firmware turns out to be such a radically different design that it makes it extremely difficult, if not impossible, to carry over very much of the rather large API built into NQC to (...) (18 years ago, 31-Jan-06, to lugnet.robotics)
|
24 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
