On 01/07/16 08:07, bitwise wrote:
Sorry I haven't had much time to work on this lately. I'm not sure how
soon I will have time. If anyone else wanted to champion this effort, we
could discuss passing the torch and trying to make use of the work I've
done thus far. I still plan to do it at some
On Friday, 1 July 2016 at 06:07:13 UTC, bitwise wrote:
On Monday, 27 June 2016 at 11:02:33 UTC, Guillaume Piolat wrote:
Unloading of shared libraries on OS X continues to be a
problem though, it would be nice if it worked in 64-bit.
Sorry I haven't had much time to work on this lately. I'm
On Monday, 27 June 2016 at 11:02:33 UTC, Guillaume Piolat wrote:
Unloading of shared libraries on OS X continues to be a problem
though, it would be nice if it worked in 64-bit.
Sorry I haven't had much time to work on this lately. I'm not
sure how soon I will have time. If anyone else wanted
On 27/06/16 21:22, Guillaume Piolat wrote:
My wording was a bit strong.
As you may remember, the workaround involved "leaking" the dynlib.
On OS X I keep having a lingering crash which is a bit random, happens
with multiple instantiation/closing of a dynlib. It is a bit hard to
reproduce and
On Monday, 27 June 2016 at 18:59:35 UTC, Jacob Carlborg wrote:
On 27/06/16 13:02, Guillaume Piolat wrote:
Unloading of shared libraries on OS X continues to be a
problem though,
it would be nice if it worked in 64-bit.
I know the current situation is not ideal, but does it cause
any
On 27/06/16 13:02, Guillaume Piolat wrote:
Unloading of shared libraries on OS X continues to be a problem though,
it would be nice if it worked in 64-bit.
I know the current situation is not ideal, but does it cause any problems?
--
/Jacob Carlborg
