[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gnulib-bug
Subject:    Re: [Bug-gnulib] full_write how to distingush EOF?
From:       "Oskar Liljeblad" <oskar () osk ! mine ! nu>
Date:       2004-09-26 8:29:09
Message-ID: 20040926082909.GA22755 () oskar
[Download RAW message or body]

On Sunday, September 26, 2004 at 01:14, Paul Eggert wrote:
> 
> > How do you distinguish an EOF from a "no free space" error with
> > full_write? It seems to me that it is more important to be able
> > to do this rather than support broken systems.
> 
> Can you give more details about the problem?  'write' can't fail due
> to EOF, right?  (Are you worried about the case where the buffer size
> is zero?)

Looks like I need to read up on unix (and socket programming in particular).
I was under the impression that write would return 0/EOF when writing to
a disconnected socket. But now I know better... Please ignore the email.

Regards,

Oskar Liljeblad (oskar@osk.mine.nu)



[prev in list] [next in list] [prev in thread] [next in thread]