Marc Lehmann wrote: >> That seems rather undesirable for many applications. > > Well, its arguably better than libevents behaviour, which is simply > returning from event_loop, leaving the app unclear on what has happened > and what to do. > > In any case, you can get the same behaviour as libevent by calling unloop > in case of an error, so the interface is strictly more powerful.
Another reason this is undesirable: to get the libevent behavior, I'd have to have this logic in *every callback* to get the same behavior. _______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkey.org/mailman/listinfo/libevent-users
