Re: [Boost-users] [signals2] scoped_connection strangeness

Subject: Re: [Boost-users] [signals2] scoped_connection strangeness
From: Igor R (boost.lists_at_[hidden])
Date: 2010-06-25 10:53:20

> There isn't a way right now. Â It would require adding a method to signals to
> do a cleanup, plus a method to wait for any concurrent invocations to
> complete.

Why to wait?
I mean the following use case:

my_slot::conect()
{
  conection_ = asyncSubsystem_.signal_.connect(&listener::handler,
smart_ptr_from_this());
}

my_slot::disconnect()
{
  conection_.disconnect();
  asyncSubsystem_.signal_.cleanup();
}

All I want here is that after I call my_slot::disconnect, the my_slot
instance (being managed by means of some smart ptr) will die sooner or
later.