Re: [Boost-users] [signals2][review] The review of the signals2 library (formerly thread_safe_signals) begins today, Nov 1st

Subject: Re: [Boost-users] [signals2][review] The review of the signals2 library (formerly thread_safe_signals) begins today, Nov 1st
From: Nat Goodspeed (nat_at_[hidden])
Date: 2009-10-20 16:46:17

Frank Mori Hess wrote:

> there would also need to to be a method which 
> blocks until all currently in progress signal invocations complete (which 
> might be useful to have anyways).

Does that mean you're musing about a possible implementation?

> Can you use a shared_ptr with a custom deleter to unload your dll an ensure it 
> is not unloaded while it is still referenced?

I'm not sure I understand, but let me answer as if I do. The shared_ptr 
bound into the boost::bind() object stored in the signal's slot is just 
an ordinary shared_ptr to a heap object. It doesn't know it comes from a 
DLL, nor am I especially keen to tell it.

I think the specific trouble is that my object's destructor is inlined 
in the DLL code.