2008-08-08 02:59:32 +00:00
|
|
|
/////////////////////////////////////////////////////////////////////////////
|
|
|
|
// Name: wx/tls.h
|
|
|
|
// Purpose: wxTLS_TYPE()
|
|
|
|
// Author: Vadim Zeitlin
|
|
|
|
// RCS-ID: $Id$
|
2010-07-13 13:29:13 +00:00
|
|
|
// Licence: wxWindows licence
|
2008-08-08 02:59:32 +00:00
|
|
|
/////////////////////////////////////////////////////////////////////////////
|
|
|
|
|
|
|
|
/**
|
|
|
|
Macro to be used for thread-specific variables declarations.
|
|
|
|
|
|
|
|
This macro can be used to define thread-specific variables of the specified
|
2008-08-29 23:28:42 +00:00
|
|
|
@a type. Such variables must be global or static and must be POD, i.e.
|
|
|
|
not have any constructors or destructor (even implicitly generated by the
|
|
|
|
compiler due to use of base classes or members which are not POD in a
|
|
|
|
struct).
|
|
|
|
|
|
|
|
Example of use:
|
2008-08-08 02:59:32 +00:00
|
|
|
@code
|
|
|
|
struct PerThreadData
|
|
|
|
{
|
|
|
|
... data which will be different for every thread ...
|
|
|
|
};
|
|
|
|
|
2008-08-29 23:28:42 +00:00
|
|
|
static wxTLS_TYPE(PerThreadData) s_threadDataVar;
|
|
|
|
#define s_threadData (wxTLS_VALUE(s_threadDataVar))
|
|
|
|
|
|
|
|
... use s_threadData as a variable of type PerThreadData ...
|
2008-08-08 02:59:32 +00:00
|
|
|
@endcode
|
|
|
|
|
2008-08-29 23:28:42 +00:00
|
|
|
Notice that the use of the ugly wxTLS_VALUE() macro is unfortunately
|
|
|
|
required if you need to support platforms without native compiler support
|
|
|
|
for thread-specific variables. If you compile your code only on platforms
|
|
|
|
which do have such support (recent versions of GNU C++ compiler, Microsoft
|
|
|
|
Visual C++ and Sun C++ compiler are known to have it), you can avoid it and
|
|
|
|
use the variable directly.
|
|
|
|
*/
|
|
|
|
#define wxTLS_TYPE(type) compiler-dependent-implementation
|
|
|
|
|
|
|
|
/**
|
|
|
|
Macro to access thread-specific variables.
|
|
|
|
|
|
|
|
This macro is used to hide the difference in implementation of
|
|
|
|
thread-specific variables under different platforms: they can be of type T
|
|
|
|
used in wxTLS_TYPE() if they are directly supported by the compiler or of
|
|
|
|
type emulating @c T @c *, i.e. a pointer to this type otherwise. This macro
|
|
|
|
always returns an expression of type @c T itself.
|
|
|
|
|
2008-08-30 12:44:43 +00:00
|
|
|
As shown in wxTLS_TYPE() example, you may want to @c \#define a symbol
|
2008-08-29 23:28:42 +00:00
|
|
|
wrapping a thread-specific variable with this macro. And, as also explained
|
|
|
|
in wxTLS_TYPE() documentation, you may avoid using it entirely if you
|
|
|
|
target only recent compilers.
|
|
|
|
|
|
|
|
@see wxTLS_PTR()
|
2008-08-08 02:59:32 +00:00
|
|
|
*/
|
2008-08-29 23:28:42 +00:00
|
|
|
#define wxTLS_VALUE(var)
|
|
|
|
|
|
|
|
/**
|
|
|
|
Macro to return address of a thread-specific variables.
|
|
|
|
|
|
|
|
This macro is similar to wxTLS_VALUE() except that it always returns a
|
|
|
|
pointer to the type of thread-specific variable.
|
2008-08-08 02:59:32 +00:00
|
|
|
|
2008-08-29 23:28:42 +00:00
|
|
|
Notice that this is not a constant expression even if the macro is defined
|
|
|
|
simply as @c &var -- the value returned is still different for every
|
|
|
|
thread.
|
|
|
|
*/
|
|
|
|
#define wxTLS_PTR(var)
|