Re: Creating thread from a class object

From:

"Ben Voigt" <rbv@nospam.nospam>

Newsgroups:

microsoft.public.vc.language

Date:

Wed, 10 Jan 2007 13:02:13 -0600

Message-ID:

<eikK2mONHHA.3944@TK2MSFTNGP06.phx.gbl>

"David Lowndes" <DavidL@example.invalid> wrote in message
news:8q5aq2hekv8lko90nllmc8msro872cr3n9@4ax.com...

You could make the method static, but that's probably no more useful
than having a global function in the first place.

What you may find more useful is to pass a pointer to an instance of
the class to the thread function when you create the thread.

Why not both? A static member function has access to the non-public
members
as well, if you pass a pointer to an instance of the particular class.

A static method only has access to static members. I think it'd be
confusing - imagine maintaining it if you're not familiar with it or
C++.

Not at all. Any class member function, whether static or not, has full
privilege to access private members, including static member functions and
data, and non-static member functions and data of any instance of the class.
The fact that non-static functions always know of at least one instance (the
this pointer) and static functions does not decrease the ability of static
functions to reach inside arguments, globals, and so forth having that type
and use all the private members.

While you might be able to implement stream insertion operators (ie cout <<
o) using only the public interface, the fact is that static member functions
can use the private interface as well.

Of course, you're free to do whatever is possible.

Dave