"Mark Hammond" <mhammond@skippinet.com.au> writes:
>> etc). But I
>> > believe we could simply lean on them for their
>> implementations at runtime.
>>
>> Ah, so that void (*funcTLSAlloc)(...) was supposed to be something
>> supplied by the extension writer?
>>
>> Hmm, the Boost interface doesn't work that way, and AFAICT wouldn't be
>> easily adapted to it.
>
> Windows and Mozilla work as you describe too, but I don't see the problem.
> For both of these, we would just provide a 3 <wink> line stub function,
> which uses the platform TLS API to return a "void *" we previously stashed.
> This local function is passed in.
I can't really imagine what you're suggesting here. Code samples
help.
> But yeah, as I said before, happy to YAGNI it.
Not sure what "it" is supposed to be here, either.
--
David Abrahams
dave@boost-consulting.com * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4