 | | Re: thread class for legOS —John A. Tamplin
|
| | | (...) No, static doesn't matter but it is possible the calling conventions of C and C++ might be different (I don't know of a platform where that is the case for a an extern function), so you might need to specify C linkage, as in: extern "C" int (...) (22 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| | | |
| | | | | Re: thread class for legOS —Michael Ash
|
| | | | (...) 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 (...) (22 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: thread class for legOS —John A. Tamplin
|
| | | | (...) 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 (...) (22 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: thread class for legOS —Michael Ash
|
| | | | (...) 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 (...) (22 years ago, 22-Jan-02, to lugnet.robotics.rcx.legos)
|
| | | | |
