From: "Sean Charles" <[EMAIL PROTECTED]>
> I have had a bad day and your attitude
> is just not called for I think.
It's not an "attitude." It's a recognition of the purpose of mailing
lists/newsgroups/forums, and that many/most prefer to keep things
subject-focused. There are plenty of C++ resources elsewhere--better ones,
in fact, than this list (seeing as how the poor guy received one wrong
response!).
Anyone, I didn't invent this "attitude." It's been expressed by many folks
here frequently. This isn't a forum to teach C or C++, and people shouldn't
have to have their inboxes filled with such posts.
Personally, I wouldn't mind opening up the list to easy C++ questions (like
this) because I know a lot more about C++ than I do about Palm programming.
But my judgement is that this is not the desire of the list. You may
disagree, or you might not even care.
BTW, IMO it's not a good idea to post when you've had a bad day. :(
> > Never did understand why 'this' is necessary.
>
> The 'this' is necessary because the 'message send' and the 'message
> receiver' can both be specified. In my game I am nearly finishing still, I
> have calls where the 'this' is in fact some other object, not the object
> currently in execution scope. Obv. you have to send the call somewhere and
> if it ain't this it's that! Or the other...
No, you don't have to specify 'this' in member access from member code:
struct foo { void bar(); void test() { bar(); /* no 'this' necessary
*/ } };
But you always have to specify 'this' with pointers to member functions,
even from member code, and I can't remember the justification for that.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
