Issue 5337 - Documentation regarding interfacing with C does not account for TLS differences

Author: WalterBright

interfaceToC.dd

@@ -429,20 +429,6 @@ void foo(char[] string) {
 	do the right shift and masks.
 	)
 
-$(V1
-<hr>
-<h1>Interfacing to C++</h1>
-
-	$(P D does not provide an interface to C++, other than
-	through $(DPLLINK COM.html, COM programming). Since D, however,
-	interfaces directly to C, it can interface directly to
-	C++ code if it is declared as having C linkage.
-	)
-
-	$(P D class objects are incompatible with C++ class objects.
-	)
-)
-
 <h2>$(LNAME2 Using C Libraries, Using Existing C Libraries)</h2>
 
 	$(P Since D can call C code directly, it can also call any C library
@@ -457,6 +443,35 @@ $(V1
 	to the Deimos Project.
 	)
 
+<h2>$(LNAME2 C Globals, Accessing C Globals)</h2>
+
+	$(P C globals can be accessed directly from D. C globals have the C naming
+	convention, and so must be in an $(D extern (C)) block.
+	Use the $(D extern) storage class to indicate that the global is allocated
+	in the C code, not the D code.
+	$(V2 C globals default to being in global, not thread local, storage.
+	To reference global storage
+	from D, use the $(D __gshared) storage class.)
+	)
+
+---
+extern (C) extern __gshared int x;
+---
+
+$(V1
+<hr>
+<h1>Interfacing to C++</h1>
+
+	$(P D does not provide an interface to C++, other than
+	through $(DPLLINK COM.html, COM programming). Since D, however,
+	interfaces directly to C, it can interface directly to
+	C++ code if it is declared as having C linkage.
+	)
+
+	$(P D class objects are incompatible with C++ class objects.
+	)
+)
+
 )
 
 Macros: