So this finally solves the fundamental problem regarding a race on initialisation of the thread-wrapper; it does *not* solve the same problem for classes deriving from thread-wrapper, which renders this design questionable altogether -- but this is another story. In the end, this initialisation-race is rooted in the very nature of starting a thread; it seems there are the two design alternatives: - expose the thread-creation directly to user code (offloading the responsibility) - offer building blocks which are inherently dangerous |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||