🚀 go-pugleaf

>What exactly are you trying to accomplish in the first place?  Typically,
>wrapping the thread in its own class is much more flexible than using TLS.
>Then you can put whatever you want into the class.  TLS is typiucally only
>used by the OS for its own internal uses (storing COM thread concurrency
>flags, GetLastError() error codes, etc).

Hi Gambit,
I am at the design phase of simulating a microcontroller. One thread
will handle the main program while each interrupt service routine will
get its own thread, so that they can interrupt each other "like in the
real world".
The whole concept is still somewhat misty and at one point in time I
thought I might need TLS - or rather learn enough about TLS to be able
to judge whether it would be helpful here.
The problematic part for the moment is that all these threads will do
some reporting (we want to know what's going one) and this is the
bottleneck right now: they can (and will) interrupt each other there
and I want a robust design which can be carried over to "Version 2"
(when we add simulating an RTOS - Real Time OS - on top of this).

We'll just leave it at this point for the moment. I'm at the drawing
board drawing little pictures ...
Best regards
Helmut Giese