On Thursday, 17 September 2015 at 16:54:09 UTC, ponce wrote:
On Thursday, 17 September 2015 at 16:42:52 UTC, bitwise wrote:
[...]
I use static linking of druntime already all the time and rely
on it to be able to do something instead of nothing (where
would I even found that shared druntime?). Apart from this one
horrible bug, static runtime seems very much working. Remove
possibilities to do work would make my situation worse.
I can call rt_init / rt_term at the right place with LDC global
constructor/destructors no problem. The problem is this
callback that cannot be removed. Don't know why it's there in
the first place since by definition a shared library can't
control when it's unloaded.
It seems that you either haven't read, or did not understand my
previous posts. This is a complicated problem, and unless you're
willing to dig much deeper into it, then you'll have to deal with
things the way they are.
Bit
