Date: Wed, 10 Mar 1999 17:30:18 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Frank Heckenbach <frank AT tim DOT gerwinski DOT de>
cc: djgpp-workers AT delorie DOT com, peter AT gerwinski DOT de
Subject: Re: Patch for select()
In-Reply-To: <57676CAB.19990310161957.FOO-3B3F.frank@goedel.fjf.gnu.de>
Message-ID: <Pine.SUN.3.91.990310172841.4977F-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 10 Mar 1999, Frank Heckenbach wrote:

> IOW, as far as I understand the semantics of select(), when it says
> `ready', it means: you can do a read() now and it won't block --
> it'll either read some data, or return 0 to indicate "EOF", or
> return an error status.

Yes, that is how I interpret the return value of `select' as well.

Thanks for the explanations.  This will hopefully be corrected in the 
next DJGPP release.