ev_ref, the other way round

Gabriel Kerneis kerneis at pps.jussieu.fr
Tue Jun 23 08:16:27 CEST 2009


On Tue, Jun 23, 2009 at 12:53:07AM +0200, Marc Lehmann wrote:
> Sounds more like a bug in the code of those users to me (_GNU_SOURCE
> is a reserved macro name, and ev.h can be included regardless of how
> _GNU_SOURCE is defined).

_GNU_SOURCE has to be defined *before* the inclusion of any other
header, and ev.h is included automatically with cpc_runtime.h at the
very begining of cpc files, so *before* anything the user might define.

There are two work-arounds: require the use to include cpc_runtime.h
himself, or define -D_GNU_SOURCE on the command-line. For some reason,
my advisor dislikes the first option, and the second one is ugly since
the information is not carried in the source code anymore. Anyway, I
agree this is not quite a bug in libev, and being able to work-around it
via macro definitions is fine to me. I was just curious about the
sig_atomic_t != int stuff.

Regards,
-- 
Gabriel Kerneis



More information about the libev mailing list