Date: Thu, 22 Jul 2021 23:43:23 -0400
On 7/22/21 11:33 PM, Phil Bouchard via Std-Proposals wrote:
>
>
> On 7/22/21 8:09 PM, Andrey Semashev via Std-Proposals wrote:
>> On 7/22/21 9:32 PM, Tony V E via Std-Proposals wrote:
>>>
>>> You can do that, but it is not thread safe. Maybe worth
>>> standardizing, maybe not.
>>
>> Boost.Signals2 is thread safe, in some sense at least.
>>
>> Though in my practice I eventually ended up replacing uses of
>> Boost.Signals2 signals with explicit callbacks. Not because I was
>> unsatisfied with Boost.Signals2 in particular, but because I found
>> the concept of signals more difficult to work with safely and more
>> difficult to maintain and debug.
>>
>
> How could you deal with asynchronous callbacks then?
>
Sorry I meant: how could you deal with inter-thread signals / slots?
>
>
> On 7/22/21 8:09 PM, Andrey Semashev via Std-Proposals wrote:
>> On 7/22/21 9:32 PM, Tony V E via Std-Proposals wrote:
>>>
>>> You can do that, but it is not thread safe. Maybe worth
>>> standardizing, maybe not.
>>
>> Boost.Signals2 is thread safe, in some sense at least.
>>
>> Though in my practice I eventually ended up replacing uses of
>> Boost.Signals2 signals with explicit callbacks. Not because I was
>> unsatisfied with Boost.Signals2 in particular, but because I found
>> the concept of signals more difficult to work with safely and more
>> difficult to maintain and debug.
>>
>
> How could you deal with asynchronous callbacks then?
>
Sorry I meant: how could you deal with inter-thread signals / slots?
-- *Phil Bouchard* Founder & CTO C.: (819) 328-4743 Fornux Logo <http://www.fornux.com>
Received on 2021-07-22 22:43:31