At 09:56 AM 2/11/2003 -0500, you wrote:
Sorry, I forget that some acronyms aren't known by everyone. TLS stands for "thread local storage", also known as TSS or "thread specific storage".
Thanks for clearing that up.
Testing and development. I compile against 5 compilers, and with both static and dynamic libraries this means compiling 10 variants at a minimum (through in both debug and release and you have 20 variants), which is time consuming. But the real kicker is that boost::thread itself is going to rely on TLS shortly, making it so you'll always need a DLL on the Windows platforms.
Understand & sympathize. What about people who want to bundle that part into their own DLL (which is largely what I'm doing)? Does it hurt to leave the build in and doc it as untested? Also, why would inclusion of TLS require it to be a DLL? It would seem like including TLS could also be done in a static lib or am I being completely obtuse? On an almost related note, I saw mention of a cooperative cancel policy from another post of yours. Do you have any ETA on that and any info on what it will support vs what it won't support? Is that info on the developer mailing list? thanks again for all your info. michael