Re: [Boost-users] [signals2] connection blocking

Subject: Re: [Boost-users] [signals2] connection blocking
From: Frank Mori Hess (frank.hess_at_[hidden])
Date: 2009-05-18 16:07:21

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 18 May 2009, Bryan Green wrote:
> Bryan Green writes:
> > I suppose I don't need the connection object at all if the widget itself
> > is trackable.  But now that I've looked at the shared_connection_block
> > code, I'm wondering, why is it noncopyable?  It looks to me like it could
> > be. If it were copyable/assignable (and ultimately, movable), I wouldn't
> > need t= o
> > dynamically allocate it.
>
> I have correct what I said here.  The problem isn't copyability (they are
> copyable).  Its that the shared_connection_block cannot be
> default-constructed.  What would be the repercussions of allowing default
> construction of shared_connection_block objects?

It probably wouldn't hurt.  In the meantime you can also use 
boost::optional<shared_connection_block> to unintrusively add an 
uninitialized state and avoid dynamic allocation.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkoRv/kACgkQ5vihyNWuA4XA7gCfTEsxme0vwOK1N0HmdVPAZcIH
JyAAoNDI3FETZ+fbvAZrExxEZpFoRgpp
=oYsq
-----END PGP SIGNATURE-----