Ideas for runtime loading of shared libraries.

Walter Bright newshound2 at digitalmars.com
Thu Mar 7 19:26:14 PST 2013


On 3/7/2013 7:22 PM, Walter Bright wrote:
> On 3/7/2013 6:18 PM, Daniel Murphy wrote:
>> What if their vtbl points into the dll code?
>>
>> What about delegates or function pointers that point there?
>
> These are problems with *any* dynamic dll code. The answer is to tell the user
> "don't do that". The user should NEVER continue to use objects created by that
> dll or delegates/functionpointers/datapointers that refer to it.


In essence, dynamically loading/unloading dlls is like calling malloc/free - it 
cannot be made @safe.


More information about the Digitalmars-d mailing list