Re: copying sigc::signals

[Jonathon Jongsma <jonathon quotidian org>]

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.

-- 
Jonathon Jongsma <jonathon quotidian org>