🚀 go-pugleaf

Ed Mulroy wrote:

>Warning:
>
>Thread Local Storage, TLS, provides a very small amount of memory.  Every 
>compiler supplies an alternate function to that provided by Win32 for 
>starting a thread.  The compiler-supplied function(s) set up a data block 
>and place the address of that block and possibly some flags into the TLS 
>memory.
>
>If you alter TLS memory you may crash the program and possibly crash the 
>machine.

Um, yeah, if you go in and trash the place, sure.. but the TLS example
code shows the thread doing LocalAlloc (which can be any size) and
placing the pointer into TLS. So, you don't actually mess with
TLStorage, just the LocalAlloc buffer.
Only advantage I see is the thread doesn't have to pass the pointer to
all of it's subroutines.

Oh, perhaps you were warning that VCL and perhaps TThread already use
that slot, and overwritting it would be problematic? So, one should
ensure TlsGetValue() == 0 before TlsSetValue(), at least for testing
purposes.

>  If you Win32 function to start the thread in a C/C++ program then 
>you also risk causing a crash.

That one didn't parse?
CreateThread()? Crashing?