core.runtime: loadLibrary and unloadLibrary?

[F i L]

On Friday, 11 January 2013 at 02:20:27 UTC, Walter Bright wrote:
> On 1/10/2013 2:42 AM, Jonathan M Davis wrote:
>> C shared libraries are fine. It's D shared libraries that are 
>> the problem. I
>> don't remember the details, but IIRC, among other things, you 
>> end up with
>> multiple copies of the GC running. The runtime needs a variety 
>> of non-trivial
>> tweaks to it order to fix those problems before shared D 
>> libraries become
>> viable.
>
>
> This was fixed in D1 long ago. DLLs would use the Executable's 
> gc instance.

Wait.. this was a bit unclear, but it sounded like you just said 
D's DLL issues where fixed awhile ago.. Is D2 capable of 
correctly loading DLLs? What's the situation with Linux?