[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[Libevent-users] evutil_closesocket() macro portability.

To: "libevent-users@xxxxxxxxxxxxx" <libevent-users@xxxxxxxxxxxxx>
Subject: [Libevent-users] evutil_closesocket() macro portability.
From: Sebastian Sjöberg <Sebastian.Sjoberg@xxxxxxxx>
Date: Wed, 24 Mar 2010 11:21:25 +0100
Accept-language: en-US, sv-SE
Acceptlanguage: en-US, sv-SE
Delivered-to: archiver@xxxxxxxx
Delivered-to: libevent-users-outgoing@xxxxxxxx
Delivered-to: libevent-users@xxxxxxxx
Delivery-date: Wed, 24 Mar 2010 06:30:10 -0400
Reply-to: libevent-users@xxxxxxxxxxxxx
Sender: owner-libevent-users@xxxxxxxxxxxxx
Thread-index: AcrLO8Igof9d2fdkSSKBjUV2d7rz/A==
Thread-topic: evutil_closesocket() macro portability.

Hi,

The EVUTIL_CLOSESOCKET() macro requires you to include unistd.h in your source for linux and I don't know what on windows. To ease portablilty wouldn't it be nice if we either turned the macro into a function or included the appropriate header where we define the macro?

I'd be happy to provide a patch for whatever behavior you would prefer.

Best regards,
Sebastian Sjöberg***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users    in the body.

Next by Author: Re: [Libevent-users] evbuffer - how to read without draining data?
Previous by thread: [Libevent-users] bufferevent_disable for event_cb?
Next by thread: [Libevent-users] how to flush output immediately?
Index(es):
- Author
- Thread