While I agree that nowadays a common reserved c++ word shouldn't be in a
header file, an easy enough workaround is to simply:
extern "C" {
#include <evdns.h>
#include <...>
}
which is my habit when pulling in any C files from C++;
It has the added benefit of ensuring that the function names don't get
mangled if you're doing some crazy linking or some such.
On 10/2/07, Roger Clark <[EMAIL PROTECTED]> wrote:
>
> At least on my system, gcc complains about 'class' being used in these
> places in evdns.h:
>
> struct evdns_server_question {
> int type;
> int class;
> char name[1];
> };
>
> and
>
> int evdns_server_request_add_reply(struct evdns_server_request *req,
> int section, const char *name, int type, int class, int ttl, int
> datalen, int is_name, const char *data);
>
> It's probably a good idea to be on the safe side and change these
> identifiers to something else. I'm sure someone else will run into the
> problem eventually.
>
> --
> Roger Clark
> [EMAIL PROTECTED]
> _______________________________________________
> Libevent-users mailing list
> Libevent-users@monkey.org
> http://monkey.org/mailman/listinfo/libevent-users
>
_______________________________________________
Libevent-users mailing list
Libevent-users@monkey.org
http://monkey.org/mailman/listinfo/libevent-users
