From: firewind <firewind AT metroid DOT dyn DOT ml DOT org>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: RHIDE -- author(s) please read this
Date: 15 Nov 1997 06:36:11 GMT
Organization: Netcom
Lines: 27
Message-ID: <64jfsr$g3o@sjx-ixn4.ix.netcom.com>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 971113121457 DOT 23305K-100000 AT is> <346e3480 DOT 11667399 AT unidui DOT uni-duisburg DOT de>
NNTP-Posting-Host: elp-tx2-02.ix.netcom.com
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Michael Mauch <michael DOT mauch AT gmx DOT de> wrote:
> On Thu, 13 Nov 1997 12:15:17 +0200 (IST), Eli Zaretskii wrote:

> > Huh?  It does work for me.  Can you give an example where it doesn't?
> > I used the test program created when you compile `select.c' in the
> > libc sources with -DTEST.

[snip]

> Strange enough that I have to check if stdout is ready for input, but it
> becomes worse if you redirect stdout as well:

> in that case, stdout never becomes ready for input and select() waits
> for 15 seconds before printing

> 1: NOT ready for input
> 1:  ready for output

I'm interested in knowing why you expect stdout (a write-only stream) to
be flagged by select() as ready for input.

-- 
[-                               firewind                                   -]
[-   email: firewind AT metroid DOT dyn DOT ml DOT org (home), firewind AT aurdev DOT com (work)  -]
[-          "You're just jealous because the voices talk to -me-."          -]
[-                   Have a good day, and enjoy your C.		            -]
[-          (on a crusade of grumpiness where grumpiness is due)            -]