|
|
 | | Re: thread class for legOS
|
| (...) Unless you define a function as a member function, there is no this parameter at all. In the example given, it was not a member function at all (nor should it be). I believe you are thinking of a static member function vs. a non-static member (...) (24 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
| | | | | RE: newbie
|
| If you decide to use LegOS you won't be needing nor will you have the chance to use NQC because a RCX with LegOS loaded won't understand nor respond to any standard firmware commands. Check (if you didn't already) the side links at: (URL) From: (...) (24 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
| | | | | RE: newbie
|
| so if i decide to use LegOS I don't need NQC, right? as I understood, de LegOS itself it's complete to be used alone.... (...) programs on RCX. (...) LEGO (...) could call (...) LEGO (...) standard LEGO (...) for (...) run some (...) don't (...) -- (...) (24 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
| | | | | RE: newbie
|
| LegOS is an operation system ( a firmware replacement in itself) It's like a mini UNIX system, that will run true C compiled programs on RCX. NQC on the other hand, all it does is translate a NQC program into LEGO pCode that will be *interpreted* by (...) (24 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
| | | | | newbie
|
| Hi everybody, I'm starting to use Lego products and I'm having problems to undrestand a few things. For example, I want to use NQC and I don't understand why the LegOS needs a C cross-compiler... or by having LegOS I don't need NQC? -- Paula Berger (...) (24 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
|
