Problem using member function when dealing with threading

[hanhao]

hi, i am new in programming and now dealing with some multi threading stuff

anyway i got problem when trying to use member function when doing threads

i searched around the net and found that 1 method is by using messages which is rather complex

another method that somebody posted is by casting:

DWORD pg_control::thr ( LPVOID lpvParam ) // static
{
    pg_control *thr = (pg_control*)lpvParam;
    
    thr->get_hosts(0,NULL);
    // Go on with code ...
    return 0;
}


void pg_control::OnNn()
{   
   AfxBeginThread (   (AFX_THREADPROC)pg_control::thr,  (LPVOID)this );}

however i get some errors

C:\Program Files\Microsoft Visual Studio\MyProjects\abc.cpp(222) : error C2440: 'type cast' : cannot convert from '' to 'unsigned int (__cdecl *)(void *)'
None of the functions with this name in scope match the target type
Error executing cl.exe.

AClient.exe - 1 error(s), 0 warning(s)

the problem lies in the red text
can anyone please correct and enlighten me?
thanks!

- using winxp programming for win98se
- MFC style
- VC++6.0 SP6

[grumpy]

Thread functions are typically normal functions (eg "void *Function(void *)"), not non-static member functions of classes. If you really want the function to be a member of a class, make it static (i.e. it will not receive a hidden `this' pointer when it is called).

[okinrus]

hi, i am new in programming and now dealing with some multi threading stuff
anyway i got problem when trying to use member function when doing threads
i searched around the net and found that 1 method is by using messages which is rather complex

If you're using MFC, using asynchronous messages requires a bit of initial work, such as deriving from CWinThread, RegisterWindowMessage, GUID's, but it's more tedious than difficult. (Difficult is sorting out the bizarre behavior when you make threading mistakes.) You might even wrapping the PostThreadMessage calls, prossibly in a proxy class, but first decide how you want the method to behave. If you want to call the method of an active object, have the method processed in the other thread, and have the method return immediately to caller, then you're want to use asynchronous messages. Otherwise, if you only want to set some data in the active object, try use a regular messsage. The setting of the data won't be handled by the active object's thread but by the caller's thread.

another method that somebody posted is by casting:

I don't think casting the function pointer is such a good idea. Can that even be done? If you're using worker threads, you're better off sending the pointer to the object in the LPVOID parameter and then casting the LPVOID to the right type.

[xErath]

arghh.. please don't mix MFC with threading.. that's awfull... I'd prefer a million times to use CreateThread.