On Tue, Oct 02, 2007 at 02:49:28AM -0400, Roger Clark wrote:
> At least on my system, gcc complains about 'class' being used in these
> places in evdns.h:
Hi, Roger! I've checked in a possible fix for this as subversion
revision r486. The fix will appear in the first 1.4 release, assuming
that i
On Tue, Oct 02, 2007 at 03:18:15PM -0400, Roger Clark wrote:
> Most of the header is already surrounded with extern "C", but not the
> offending part. Just wanted to give someone a heads up.
I just changed it, but it doesn't do any good. My understanding is
that 'extern "C"' is only for linkage,
Most of the header is already surrounded with extern "C", but not the
offending part. Just wanted to give someone a heads up.
On 10/2/07, Rick R <[EMAIL PROTECTED]> wrote:
> While I agree that nowadays a common reserved c++ word shouldn't be in a
> header file, an easy enough workaround is to simp
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
#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
mang
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,
