From b725625e6fc29fc38e561f1c8455f4559add4d5e Mon Sep 17 00:00:00 2001 From: William S Fulton Date: Fri, 8 Feb 2013 06:34:35 +0000 Subject: Add support for thread_local when specified with other legitimate storage class specifiers - extern and static --- Doc/Manual/Cpp0x.html | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) (limited to 'Doc/Manual') diff --git a/Doc/Manual/Cpp0x.html b/Doc/Manual/Cpp0x.html index e9576ec84..457a7e41d 100644 --- a/Doc/Manual/Cpp0x.html +++ b/Doc/Manual/Cpp0x.html @@ -722,17 +722,22 @@ OutputType var3 = 3.1416_suffix;

7.2.20 Thread-local storage

-

SWIG correctly parses the thread_local keyword. For example, a variable +

SWIG correctly parses the thread_local keyword. For example, variable reachable by the current thread can be defined as:

 struct A {
-   thread_local int val;
+   static thread_local int val;
 };
+thread_local int global_val;
-

The new C++0x threading libraries are ignored because each SWIG target language offers -its own threading facilities.

+

+The use of the thread_local storage specifier does not affect the wrapping process; it does not modify +the wrapper code compared to when it is not specified. +A variable will be thread local if accessed from different threads from the target language in the +same way that it will be thread local if accessed from C++ code. +

7.2.21 Defaulting/deleting of standard functions on C++ objects

-- cgit v1.2.3