What about creating a new initialization function that would take options via flags with one of them indicating that you don't want libevent to set up any signal handling stuff. We could name it something like event_init_advanced, or event_init_with_flags, or something like that. We would then need to update the libevent internals to skip evsignal_init if the "no signals" flag was present. With this approach we wouldn't break any existing code, as event_init would continue to function as it does today, and developers would have the flexibility to choose to use libevent signal handling in the future.
I could whip up a patch for this if this seems like a good idea. Andrew
_______________________________________________ Libevent-users mailing list [email protected] http://monkey.org/mailman/listinfo/libevent-users
