#include <thread.h>
Inheritance diagram for Thread::
Public Methods | |
| CCXX_MEMBER_EXPORT (CCXX_EMPTY) Thread(bool isMain) | |
| This is actually a special constructor that is used to create a thread "object" for the current execution context when that context is not created via an instance of a derived Thread object itself. More... | |
| CCXX_MEMBER_EXPORT (CCXX_EMPTY) Thread(int pri=0, size_t stack=0) | |
| When a thread object is contructed, a new thread of execution context is created. More... | |
| Thread (const Thread &th) | |
| A thread of execution can also be specified by cloning an existing thread. More... | |
| CCXX_MEMBER_EXPORT (virtual)~Thread() | |
| The thread destructor should clear up any resources that have been allocated by the thread. More... | |
| CCXX_MEMBER_EXPORT (int) Start(Semaphore *start=0) | |
| When a new thread is created, it does not begin immediate execution. More... | |
| CCXX_MEMBER_EXPORT (int) Detach(Semaphore *start=0) | |
| Start a new thread as "detached". More... | |
| Thread * | getParent (void) |
| Gets the pointer to the Thread class which created the current thread object. More... | |
| CCXX_MEMBER_EXPORT (void) Suspend(void) | |
| Suspends execution of the selected thread. More... | |
| CCXX_MEMBER_EXPORT (void) Resume(void) | |
| Resumes execution of the selected thread. More... | |
| thread_cancel_t | getCancel (void) |
| Used to retrieve the cancellation mode in effect for the selected thread. More... | |
| bool | isRunning (void) |
| Verifies if the thread is still running or has already been terminated but not yet deleted. More... | |
| bool | isThread (void) |
| Tests to see if the current execution context is the same as the specified thread object. More... | |
| friend | CCXX_EXPORT (throw_t) getException(void) |
| Get exception mode of the current thread. More... | |
| friend | CCXX_EXPORT (void) setException(throw_t mode) |
| Set exception mode of the current thread. More... | |
| friend | CCXX_EXPORT (void) ccxx_sleep(timeout_t msec) |
| Thread safe sleep call replacement. More... | |
Protected Methods | |
| virtual void | Run (void)=0 |
| All threads execute by deriving the Run method of Thread. More... | |
| CCXX_MEMBER_EXPORT (virtual void) Final(void) | |
| A thread that is self terminating, either by invoking Exit() or leaving it's Run(), will have this method called. More... | |
| CCXX_MEMBER_EXPORT (virtual void) Initial(void) | |
| The initial method is called by a newly created thread when it starts execution. More... | |
| CCXX_MEMBER_EXPORT (virtual void *) getExtended(void) | |
| Since getParent() and getThread only refer to an object of the Thread "base" type, this virtual method can be replaced in a derived class with something that returns data specific to the derived class that can still be accessed through the pointer returned by getParent() and getThread. More... | |
| CCXX_MEMBER_EXPORT (virtual void) Notify(Thread *th) | |
| When a thread terminates, it now sends a notification message to the parent thread which created it. More... | |
| CCXX_MEMBER_EXPORT (void) Sleep(timeout_t msec) | |
| A thread-safe sleep call. More... | |
| void | Exit (void) |
| Used to properly exit from a Thread derived Run() or Initial() method. More... | |
| CCXX_MEMBER_EXPORT (void) Yield(void) | |
| Yields the current thread's CPU time slice to allow another thread to begin immediate execution. More... | |
| CCXX_MEMBER_EXPORT (void) testCancel(void) | |
| test a cancellation point for deferred thread cancellation. More... | |
| CCXX_MEMBER_EXPORT (void) setCancel(thread_cancel_t mode) | |
| Sets thread cancellation mode. More... | |
| CCXX_MEMBER_EXPORT (void) setSuspend(thread_suspend_t mode) | |
| Sets the thread's ability to be suspended from execution. More... | |
| CCXX_MEMBER_EXPORT (void) Terminate(void) | |
| Used by another thread to terminate the current thread. More... | |
| void | clrParent (void) |
| clear parent thread relationship. More... | |
Friends | |
| class | PosixThread |
| class | Slog |
| RETSIGTYPE | ccxx_sigsuspend (int) |
| void | execHandler (Thread *th) |
| Thread * | getThread (void) |
| int | start (Thread &th, Semaphore *start=0) |
| Start execution of a specified thread. More... | |
| void | operator++ (Thread &th) |
| Signal the semaphore that the specified thread is waiting for before beginning execution. More... | |
| void | operator-- (Thread &th) |
The base Thread class supports encapsulation of the generic threading methods implemented on various target operating systems. This includes the ability to start and stop threads in a synchronized and controllable manner, the ability to specify thread execution priority, and thread specific "system call" wrappers, such as for sleep and yield. A thread exception is thrown if the thread cannot be created. Threading was the first part of Common C++ I wrote, back when it was still the APE library. My goal for Common C++ threading has been to make threading as natural and easy to use in C++ application development as threading is in Java. With this said, one does not need to use threading at all to take advantage of Common C++. However, all Common C++ classes are designed at least to be thread-aware/thread-safe as appropriate and necessary.
Common C++ threading is currently built either from the Posix "pthread" library or using the win32 SDK. In that the Posix "pthread" draft has gone through many revisions, and many system implementations are only marginally compliant, and even then usually in different ways, I wrote a large series of autoconf macros found in ost_pthread.m4 which handle the task of identifying which pthread features and capabilities your target platform supports. In the process I learned much about what autoconf can and cannot do for you..
Currently the GNU Portable Thread library (GNU pth) is not directly supported in Common C++. While GNU "Pth" doesn't offer direct native threading support or benefit from SMP hardware, many of the design advantages of threading can be gained from it's use, and the Pth pthread "emulation" library should be usable with Common C++. In the future, Common C++ will directly support Pth, as well as OS/2 and BeOS native threading API's.
Common C++ itself defines a fairly "neutral" threading model that is not tied to any specific API such as pthread, win32, etc. This neutral thread model is contained in a series of classes which handle threading and synchronization and which may be used together to build reliable threaded applications.
Common C++ defines application specific threads as objects which are derived from the Common C++ "Thread" base class. At minimum the "Run" method must be implemented, and this method essentially is the "thread", for it is executed within the execution context of the thread, and when the Run method terminates the thread is assumed to have terminated.
Common C++ allows one to specify the running priority of a newly created thread relative to the "parent" thread which is the thread that is executing when the constructor is called. Since most newer C++ implementations do not allow one to call virtual constructors or virtual methods from constructors, the thread must be "started" after the constructor returns. This is done either by defining a "starting" semaphore object that one or more newly created thread objects can wait upon, or by invoking an explicit "Start" member function.
Threads can be "suspended" and "resumed". As this behavior is not defined in the Posix "pthread" specification, it is often emulated through signals. Typically SIGUSR1 will be used for this purpose in Common C++ applications, depending in the target platform. On Linux, since threads are indeed processes, SIGSTP and SIGCONT can be used. On solaris, the Solaris thread library supports suspend and resume directly.
Threads can be canceled. Not all platforms support the concept of externally cancelable threads. On those platforms and API implementations that do not, threads are typically canceled through the action of a signal handler.
As noted earlier, threads are considered running until the "Run" method returns, or until a cancellation request is made. Common C++ threads can control how they respond to cancellation, using setCancellation(). Cancellation requests can be ignored, set to occur only when a cancellation "point" has been reached in the code, or occur immediately. Threads can also exit by returning from Run() or by invoking the Exit() method.
Generally it is a good practice to initialize any resources the thread may require within the constructor of your derived thread class, and to purge or restore any allocated resources in the destructor. In most cases, the destructor will be executed after the thread has terminated, and hence will execute within the context of the thread that requested a join rather than in the context of the thread that is being terminated. Most destructors in derived thread classes should first call Terminate() to make sure the thread has stopped running before releasing resources.
A Common C++ thread is normally canceled by deleting the thread object. The process of deletion invokes the thread's destructor, and the destructor will then perform a "join" against the thread using the Terminate() function. This behavior is not always desirable since the thread may block itself from cancellation and block the current "delete" operation from completing. One can alternately invoke Terminate() directly before deleting a thread object.
When a given Common C++ thread exits on it's own through it's Run() method, a "Final" method will be called. This Final method will be called while the thread is "detached". If a thread object is constructed through a "new" operator, it's final method can be used to "self delete" when done, and allows an independent thread to construct and remove itself autonomously.
A special global function, getThread, is provided to identify the thread object that represents the current execution context you are running under. This is sometimes needed to deliver signals to the correct thread. Since all thread manipulation should be done through the Common C++ (base) thread class itself, this provides the same functionality as things like "pthread_self" for Common C++.
Common C++ threads are often aggregated into other classes to provide services that are "managed" from or operate within the context of a thread, even within the Common C++ framework itself. A good example of this is the TCPSession class, which essentially is a combination of a TCP client connection and a separate thread the user can define by deriving a class with a Run() method to handle the connected service. This aggregation logically connects the successful allocation of a given resource with the construction of a thread to manage and perform operations for said resource.
Threads are also used in "service pools". In Common C++, a service pool is one or more threads that are used to manage a set of resources. While Common C++ does not provide a direct "pool" class, it does provide a model for their implementation, usually by constructing an array of thread "service" objects, each of which can then be assigned the next new instance of a given resource in turn or algorithmically.
Threads have signal handlers associated with them. Several signal types are "predefined" and have special meaning. All signal handlers are defined as virtual member functions of the Thread class which are called when a specific signal is received for a given thread. The "SIGPIPE" event is defined as a "Disconnect" event since it's normally associated with a socket disconnecting or broken fifo. The Hangup() method is associated with the SIGHUP signal. All other signals are handled through the more generic Signal().
Incidently, unlike Posix, the win32 API has no concept of signals, and certainly no means to define or deliver signals on a per-thread basis. For this reason, no signal handling is supported or emulated in the win32 implementation of Common C++ at this time.
In addition to TCPStream, there is a TCPSession class which combines a thread with a TCPStream object. The assumption made by TCPSession is that one will service each TCP connection with a separate thread, and this makes sense for systems where extended connections may be maintained and complex protocols are being used over TCP.
|
|
A thread of execution can also be specified by cloning an existing thread. The existing thread's properties (cancel mode, priority, etc), are also duplicated.
|
|
|
Thread safe sleep call replacement. This is mapped into sleep().
|
|
|
Set exception mode of the current thread.
|
|
|
Get exception mode of the current thread.
|
|
|
Resumes execution of the selected thread.
|
|
|
Suspends execution of the selected thread. Pthreads do not normally support suspendable threads, so the behavior is simulated with signals. On systems such as Linux that define threads as processes, SIGSTOP and SIGCONT may be used. |
|
|
Start a new thread as "detached". This is an alternative Start() method that resolves some issues with later glibc implimentations which incorrectly impliment self-detach.
|
|
|
When a new thread is created, it does not begin immediate execution. This is because the derived class virtual tables are not properly loaded at the time the C++ object is created within the constructor itself, at least in some compiler/system combinations. The thread can either be told to wait for an external semaphore, or it can be started directly after the constructor completes by calling the Start() method.
|
|
|
The thread destructor should clear up any resources that have been allocated by the thread. The desctructor of a derived thread should begin with Terminate() and is presumed to then execute within the context of the thread causing terminaton. |
|
|
When a thread object is contructed, a new thread of execution context is created. This constructor allows basic properties of that context (thread priority, stack space, etc) to be defined. The starting condition is also specified for whether the thread is to wait on a semaphore before begining execution or wait until it's start method is called.
|
|
|
This is actually a special constructor that is used to create a thread "object" for the current execution context when that context is not created via an instance of a derived Thread object itself. This constructor does not support First.
|
|
|
Used by another thread to terminate the current thread. Termination actually occurs based on the current setCancel() mode. When the current thread does terminate, control is returned to the requesting thread. Terminate() should always be called at the start of any destructor of a class derived from Thread to assure the remaining part of the destructor is called without the thread still executing. |
|
|
Sets the thread's ability to be suspended from execution. The thread may either have suspend enabled (THREAD_SUSPEND_ENABLE) or disabled (THREAD_SUSPEND_DISABLE).
|
|
|
Sets thread cancellation mode. Threads can either be set immune to termination (THREAD_CANCEL_DISABLED), can be set to terminate when reaching specific "thread cancellation points" (THREAD_CANCEL_DEFERRED) or immediately when Terminate is requested (THREAD_CANCEL_IMMEDIATE).
|
|
|
test a cancellation point for deferred thread cancellation.
|
|
|
Yields the current thread's CPU time slice to allow another thread to begin immediate execution.
|
|
|
A thread-safe sleep call. On most Posix systems, "sleep()" is implimented with SIGALRM making it unusable from multipe threads. Pthread libraries often define an alternate "sleep" handler such as usleep(), nanosleep(), or nap(), that is thread safe, and also offers a higher timer resolution.
|
|
|
When a thread terminates, it now sends a notification message to the parent thread which created it. The actual use of this notification is left to be defined in a derived class.
|
|
|
Since getParent() and getThread only refer to an object of the Thread "base" type, this virtual method can be replaced in a derived class with something that returns data specific to the derived class that can still be accessed through the pointer returned by getParent() and getThread.
|
|
|
The initial method is called by a newly created thread when it starts execution. This method is ran with deferred cancellation disabled by default. The Initial method is given a seperate handler so that it can create temporary objects on it's own stack frame, rather than having objects created on Run() that are only needed by startup and yet continue to consume stack space.
|
|
|
A thread that is self terminating, either by invoking Exit() or leaving it's Run(), will have this method called. It can be used to self delete the current object assuming the object was created with new on the heap rather than stack local, hence one may often see Final defined as "delete this" in a derived thread class. A Final method, while running, cannot be terminated or cancelled by another thread.
|
|
|
Used to properly exit from a Thread derived Run() or Initial() method. Terminates execution of the current thread and calls the derived classes Final() method. |
|
|
All threads execute by deriving the Run method of Thread. This method is called after Initial to begin normal operation of the thread. If the method terminates, then the thread will also terminate after notifying it's parent and calling it's Final() method.
|
|
|
clear parent thread relationship.
|
|
|
Used to retrieve the cancellation mode in effect for the selected thread.
|
|
|
Gets the pointer to the Thread class which created the current thread object.
|
|
|
Verifies if the thread is still running or has already been terminated but not yet deleted.
|
|
|
Tests to see if the current execution context is the same as the specified thread object.
|
|
|
|
|
|
|
|
|
|
|
|
Reimplemented in PosixThread. |
|
|
|
|
|
Signal the semaphore that the specified thread is waiting for before beginning execution.
|
|
|
|
|
||||||||||||
|
Start execution of a specified thread.
|
1.2.10 written by Dimitri van Heesch,
© 1997-2001