| |
In article <37DE2468.66B220C4@sundayta.co.uk>, David Warnock
<david@sundayta.co.uk> wrote:
> I just wondered whether it might be handy to add OnFwdFor(motors) and
> OnRevFor(motors).
If anyone wants to add these functions into their own code...
void OnFwdFor(const int m, const int &t) { Fwd(m); OnFor(m, t); }
void OnRevFor(const int m, const int &t) { Rev(m); OnFor(m, t); }
These should be efficient - everything will be inlined and no temporaries
will be created - unless a temporary is needed during the computation of
t...
int x, y;
OnFwdFor(x); // ok, no temporary
OnFwdFor(x+y); // need temp to compute x+y
Dave
--
reply to: dbaum at enteract dot com
|
|
| |
Dave,
Thanks for all the comments in the thread. As I have not looked at the
API supplied by the firmware I did not realise that the NQC api was such
a close match.
Adding the functions as you have suggested is a very neat solution.
It is nice to have alternatives in coding so that we can either just use
the primitives (Fwd, On, OnFor) where we learn less functions but write
more code (sometimes) or where we can use more complex functions such as
OnFwd and OnFwdFor.
The API for NQC 2.0 does seem very clean and I will be using it for all
future projects.
I found NQC 1.x good with my older son (age 7) within the RCX Command
Centre, although my younger son (5) is much better with the Lego
interface (and lots of help).
Many thanks
Dave
--
David Warnock
Sundayta Ltd
|
|
|
