>Proposed patch adds new flag to loop creation, that tells about early
>evpipe 
>alocation. If libev can't successfully handle this (create eventfd/pipe
>at 
>ev_loop_new), then its just return null. If all is ok, then
>ev_async_start 
>won't abort my app, because evpipe is already allocated.

Wouldn't it be better to just call the async event handler with the EV_ERROR 
flag set in the error case?

-- 
Beste Grüße,
Thilo Schulz

_______________________________________________
libev mailing list
[email protected]
http://lists.schmorp.de/mailman/listinfo/libev

Reply via email to