[zeromq-dev] libzmq - allocations, exceptions, alloc_assert and such

2015-01-27 Thread Thomas Rodgers
I know sustrik has previously railed on this topic, but at the risk of rehashing some of that ground... My reading of libzmq's source suggests that it goes to some lengths to prevent raising C++ exceptions, which, given that the C API functions do not attempt to guard ag

Re: [zeromq-dev] libzmq - allocations, exceptions, alloc_assert and such

2015-01-28 Thread Pieter Hintjens
To understand correctly, we don't propagate such failures (as exceptions or error returns), and even if we did, it'd be pointless... FWIW we added quite a lot handling in CZMQ to handle memory exhaustion. I don't particularly like that, as it makes things complex and it's unclear that there's any

Re: [zeromq-dev] libzmq - allocations, exceptions, alloc_assert and such

2015-01-28 Thread Thomas Rodgers
> > To understand correctly, we don't propagate such failures (as > exceptions or error returns), and even if we did, it'd be pointless... My thinly veiled agenda here is - We are already toast in this case anyway, can we just get rid of the extra complexity that comes with trying pretend we can

Re: [zeromq-dev] libzmq - allocations, exceptions, alloc_assert and such

2015-01-30 Thread Pieter Hintjens
Sounds good to me. The extra complexity makes things more fragile IMO. On Wed, Jan 28, 2015 at 8:16 PM, Thomas Rodgers wrote: >> To understand correctly, we don't propagate such failures (as >> exceptions or error returns), and even if we did, it'd be pointless... > > > My thinly veiled agenda he