On Wed, Apr 14, 2010 at 5:05 AM, Sebastian Sjöberg
wrote:
> On Apr 14, 2010, at 7:39 AM, Nick Mathewson wrote:
>
>> On Wed, Mar 24, 2010 at 6:21 AM, Sebastian Sjöberg
>> wrote:
>>> Hi,
>>>
>>> The EVUTIL_CLOSESOCKET() macro requires you to include unistd.h in your
>>> source for linux and I don'
On Apr 14, 2010, at 7:39 AM, Nick Mathewson wrote:
> On Wed, Mar 24, 2010 at 6:21 AM, Sebastian Sjöberg
> wrote:
>> 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
On Wed, Mar 24, 2010 at 6:21 AM, Sebastian Sjöberg
wrote:
> 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
>
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 pro
