On 07/05/2010 11:17 AM, Stefan Strasser wrote:
Zitat von Andrey Semashev <andrey.semashev@gmail.com>:
in that case, I guess I am suggesting to add a public interface like static_thread_specific_ptr, to support the semantics of __declspec(thread)/__thread/thread_local, i.e. crash when used from delay-loaded modules on platforms that don't support it.
That is a different extension from what I am proposing. But frankly speaking, I don't see much use from it if it crashes on some setups and I can't detect such setups in my code that uses this component.
I could reply to this in terms of content, but this is easier: what you're saying by that is that declspec(thread)/... make no sense on platforms that don't support delay-loading with static TSS, and was/will never be used. that's obviously not the case.
What I'm saying is that it makes little use for library writers if it doesn't allow to detect the faulty platforms. Or fallback to explicit API usage on such platforms. But that's getting OT.