Re: [boost] Interest in non-intrusive signal/slot lib?

Subject: Re: [boost] Interest in non-intrusive signal/slot lib?
From: Edward Diener (eldiener_at_[hidden])
Date: 2015-05-13 15:38:37

On 5/12/2015 2:14 PM, Emil Dotchevski wrote:
> On Tue, May 12, 2015 at 8:49 AM, Edward Diener <eldiener_at_[hidden]>
> wrote:
>
>> On 5/11/2015 10:25 PM, Emil Dotchevski wrote:
>>
>>> Hello,
>>>
>>> I realize that Boost has Signals library already, but I've implemented a
>>> non-intrusive one which approaches the problem differently, and I'm pretty
>>> sure that there is no overlap between the two. It turned out more generic
>>> than I originally anticipated, so I thought I'd ask if others would find
>>> it
>>> useful as well.
>>>
>>
>> What do you mean by non-intrusive versus the signals2 library ?
>
>
> As far as I can tell in Signals2 to emit a signal you must have access to
> the signal object, while synapse::emit takes an emitter object. For
> example, with Synapse you could write:
>
> QPushButton * b;
> ......
> synapse::emit<button_clicked>(b);
>
> (Of course emit<> has no use for the type of its emitter argument -- the
> above would work just as well with a void pointer.)

It looks interesting but without a documented  explanation I cannot 
figure out how it works. I don't think that one page of introduction, 
some examples and a reference is adequate. You should write something 
about what the parts of your system are, how they relate, and how they 
are used. I assume they form some sort of signal/slot system.