> 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. But yeah, as I said before, happy to YAGNI it. Mark.
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