core.runtime: loadLibrary and unloadLibrary?

[Sean Kelly]

I think the main issue is scanning static memory segments in the shared library during collections. Pretty sure this is sorted for Windows, but I think work still needs to be done for other platforms.  It's been a while since I've looked at this code though. Other things may be needed as well. Either way, if your D shared library is operating as if it were a C library then you should be fine. The trick is getting all shared libraries to share a single D runtime. 

On Jan 10, 2013, at 6:43 AM, "evilrat" <evilrat666 at gmail.com> wrote:

> On Thursday, 10 January 2013 at 14:07:38 UTC, Jacob Carlborg wrote:
>> On 2013-01-10 11:31, evilrat wrote:
>> 
>>> what's wrong with them? already used it on windows and mac, no problems
>>> so far, though not tested too deep, and not with D shared libs o_O
>> 
>> Apparently you haven't tested at all on Mac since it's only implemented on Windows:
>> 
>> https://github.com/D-Programming-Language/druntime/blob/master/src/rt/dmain2.d#L122
> 
> well like i said i don't used D shared libs yet.
> 
> umm.. looks simple at glance, whats the catch then if it still not implemented at least on osx?