It has been quite some time since I have been using code from code havens like code project and codeguru. Its payback time folks. Well not with something that can be readily used by all or many. But this is my sincere start.
In this article, I have tried to bring out the lack of Object Oriented Programmability in using Worker threads and overcome it. This project was more evolutionary than revolutionary. It started with the theory from Ryan Teixeira's work on Designing a Thread Class, for which I started with a basic shape. Then came the requirements for my current project for which I had to consider little/easy portability constraints.
Enough talking lets move on.
Things I wont deal here
I assume the audience is familiar with the concept of Threads / have heard of or used a worker thread atleast. My aim is to show how quick this class can bring you closer to OO Programming.
<!------------------------------- STEP 3 ---------------------------><!-- Add the article text. Please use simple formatting (
class in its declaration form looks like below. I have gone against my coding practices (which i believe is pretty much same as many programmers ) and commented the code heavily in the source files for this purpose.
DWORD Start( void* arg = NULL );
DWORD Stop ( bool bForceKill = false );
DWORD GetExitCode() const;
void Attach( LPTHREAD_START_ROUTINE lpThreadFunc );
void Detach( void );
static DWORD WINAPI EntryPoint( LPVOID pArg);
virtual DWORD Run( LPVOID arg );
virtual void ThreadCtor();
virtual void ThreadDtor();
HANDLE m_hThread; DWORD m_dwTID; LPVOID m_pUserData; LPVOID m_pParent; DWORD m_dwExitCode; };
CThreadContext m_ThreadCtx; LPTHREAD_START_ROUTINE m_pThreadFunc; };
|Uses the internal default EntryPoint static function as the ThreadFunc.|
CThread( LPTHREAD_START_ROUTINE pThreadFunc)
|The plug constructor. This is used instead of creation and a call to Attach.|
|Closes the thread object and destroys the thread. Can be changed if you dont want the thread to be terminated when the object destroys.|
DWORD Start( LPVOID pArg = NULL )
|This method starts/spawns the thread. returns any ERROR_SUCCESS if succeeded otherwise the error value as returned by GetLastError().|
DWORD Stop( bool bForceKill = false )
|This method returns the ExitCode if the thread has already terminated. the parameter optionally allows it to terminate the thread forcefully.|
DWORD GetExitCode() const
|Returns the exit code of the last thread.|
void Attach( LPTHREAD_START_ROUTINE lpThreadFunc )
I Admit, I borrowed this feature after knowing COM only. It is a great concept. Here, It is used to attach any Worker Thread function this makes the generic class itself readily usable. How? we will see soon.
void Detach( void )
|This method removes the object from any hooked worker function to the default EntryPoint static method.|
static DWORD WINAPI EntryPoint( LPVOID pArg )
|This method is the only trick you need to do to get the class contain a worker thread, others are trivial.|
virtual DWORD Run( LPVOID arg )
|The body method, this is the method that should contain your worker thread code. Note: the signature is similar to your worker thread and that arg is the user data.|
virtual void ThreadCtor()
|The mimic of a constructor for the life/scope of the thread to be spawned. you can override this method and write the Thread Level construction/initialization. This method will be called before the spawn/start of the thread.|
virtual void ThreadDtor()
|The mimic of a destructor for the life/scope of the thread spawned. you can override this method and write the Thread Level Un-initialization. This method will be called after the end of the thread.|
The best way to understand any code is through an example. So thats the way we do...
This more like a common scenario than un-usual. Lets say you have worker thread function "Threaded"
DWORD WINAPI Threaded( LPVOID lpData )
printf("worker threaded code");
And now you would like to USE & CONTROL it ( meaning its scope, life visibility etc.. ) in OO Style. This is how you would do it.
There should be a catch. Well the catch is that you lose the CTOR and DTOR mimic functions ThreadCTOR() and ThreadDTOR() functionality and you cannot access any members or methods of the encapsulated class. But still, these were not our requirments. But what if they are...
The OO Way. Even if it takes a few minutes this is the better way to do it.
You derive a class, and override only the run method and thats all there is to it. Well you may add as many members/methods you need.
class CDemoThread : public CThread
virtual DWORD Run( LPVOID arg )
printf("Threaded Object Code \n");
Now, how do you use this. Not much difference.
Things to come
I am planning to update this class with more stuff. If anyone is interested or have anything in particular, do let me know.
We shall have code that is now Object Oriented. The benefits of Object Oriented Programming is way too much to realize at an early stage (Not inviting any debates).
Hope you all will find it useful!