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 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.
--
Roger Clark
[EMAIL PROTECTED]
_______________________________________________
Libevent-users mailing list
Libevent-users@monkey.org
http://monkey.org/mailman/listinfo/libevent-users
