 | | Re: libm, windows
|
|
(...) No chance to get this running under legOS. You can do some float math like addition or multiplication but no trigonometric functions. Look in legOS/lib/float to see what can be done with the legOS floating point library. Mike (23 years ago, 24-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | libm, windows
|
|
has anyone had success with using libm in windows? I have legOS programs written from a solaris machine that compile fine and work when downloaded to the RCX, but I have not been able to compile them on a windows machine due to linking problems. The (...) (23 years ago, 24-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: thread class for legOS
|
|
(...) In the post you replied to saying "static doesn't matter", the proposal was: private: static int runWrapper(...) ; I then replied to your post, etc. Anyway, let's not degenerate into he-said-she-said. We're really just talking past each other (...) (23 years ago, 22-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: thread class for legOS
|
|
(...) In fact, neither of these suggestions will work with the code as it stands, because the runWrapper() function tries to call the Run() function, which is a non-static member function. You could pass a pointer to the class instance (this) in the (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | 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 (...) (23 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: (...) (23 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 (...) -- (...) (23 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 (...) (23 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 (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: thread class for legOS
|
|
(...) Static DOES matter; it declares the method as being a "class" method, rather than a normal instance method. I believe there is no implicit 'this' parameter and therefore it can be treated like a normal function. Of course, it can't be linked (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
