Re: copying sigc::signals

[Murray Cumming <murrayc murrayc com>]

On Fri, 2010-03-05 at 10:40 -0600, Jonathon Jongsma wrote:
> On Fri, 2010-03-05 at 14:15 +0000, Chris Vine wrote:
> > 
> > It is probably better simply to disallow copying of signals, rather
> > than do shallow copies resulting in the curious effects you mention.  I
> > took that line when writing some signal/slot classes of my own for use
> > where libsigc++ was not suitable because it is not thread safe.  (But
> > these also happen to implement trackability at the signal level.)
> 
> I think this would be my preferred solution as well, though I haven't
> really considered what all the effects of that would be.  In any case, I
> don't think the behavior is likely to change in the near future, so I
> just wanted people to be aware of the issue.

If you file a bug then we can fix it when we do ABI breaks for gtkmm 3
eventually. Of course, I'd rather have a new C++ standard real soon that
let us use its signals instead. Not likely though.


-- 
murrayc murrayc com
www.murrayc.com
www.openismus.com