Enter your search terms GNU-Darwin Web Submit search form

Widgets     Book   Threads Thread abstraction; including threads, different mutexes, conditions and thread private data. More... Compounds class   Cond class   Dispatcher   Signal class for inter-thread communication. More... class   Private class   ReaderLock   Utility class for exception-safe locking of read/write locks. More... class   Lock   Utility class for exception-safe locking of recursive mutexes. More... class   Lock   Utility class for exception-safe mutex locking. More... class   Mutex   Represents a mutex (mutual exclusion). More... class   RecMutex class   RWLock struct   StaticMutex   Like Glib::Mutex, but can be defined at compile time. More... struct   StaticPrivate struct   StaticRecMutex   Like Glib::RecMutex, but can be defined at compile time. More... struct   StaticRWLock   Like Glib::RWLock, but can be defined at compile time. More... class   Exit   Exception class used to exit from a thread. More... class   Thread   Represents a running thread. More... class   ThreadError   Exception class for thread-related errors. More... class   WriterLock   Utility class for exception-safe locking of read/write locks. More... Enumerations enum   NotLock { NOT_LOCK } enum   TryLock { TRY_LOCK } Functions void  thread_init (GThreadFunctions* vtable=0)   Initializes the GLib thread system. bool  thread_supported ()   Returns whether the thread system is initialized. Thread*  wrap (GThread* gobject) Detailed Description Thread abstraction; including threads, different mutexes, conditions and thread private data. Enumeration Type Documentation enum Glib::NotLock   Enumeration values: NOT_LOCK  enum Glib::TryLock   Enumeration values: TRY_LOCK  Function Documentation void thread_init ( GThreadFunctions*    vtable = 0 )  [inline]   Initializes the GLib thread system. Before you use a thread related function in glibmm, you should initialize the thread system. This is done by calling Glib::thread_init(). Note: You should only call thread_init() with a non-0 parameter if you really know what you are doing. thread_init() must not be called directly or indirectly as a callback from glibmm. Also no mutexes may be currently locked while calling thread_init(). thread_init() might only be called once. On the second call it will abort with an error. If you want to make sure that the thread system is initialized, you can do that too: if(!Glib::thread_supported()) Glib::thread_init(); After that line either the thread system is initialized, or the program will abort if no thread system is available in GLib, i.e. either G_THREADS_ENABLED is not defined or G_THREADS_IMPL_NONE is defined. If no thread system is available and vtable is 0 or if not all elements of vtable are non-0, then thread_init() will abort. Note: To use thread_init() in your program, you have to link with the libraries that the command pkg-config --libs gthread-2.0 outputs. This is not the case for all the other thread related functions of glibmm. Those can be used without having to link with the thread libraries. (You have to link with gthread-2.0 if you actually want to use threads in your application, though.) Parameters: vtable  A function table of type GThreadFunctions, that provides the entry points to the thread system to be used. Examples: thread/dispatcher.cc, and thread/thread.cc. bool thread_supported (   )  [inline]   Returns whether the thread system is initialized. Returns: true, if the thread system is initialized. Thread* wrap ( GThread*    gobject )  [related, inherited]