delorie.com/archives/browse.cgi | search |
Date: | Wed, 10 Mar 1999 10:43:53 +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: | <2CE741E0.19990309160234.FOO-AB9.frank@goedel.fjf.gnu.de> |
Message-ID: | <Pine.SUN.3.91.990310104329.10442G@is> |
MIME-Version: | 1.0 |
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 |
On Tue, 9 Mar 1999, Frank Heckenbach wrote: > > Could you please elaborate under what circumstances does this make a > > difference? > > Whenever a disk file is at EOF, like the test program I included. > Unpatched select() returns `not ready', but the patch makes it say > `ready', like it does under Un*x. Yes, but in what real-life situation is this important? I believe you said that you encountered the problem while porting GPC. So where did GPC need to `select' to return `ready' at EOF?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |