X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10201111815.AA23649@clio.rice.edu>
Subject: Re: frlist.c proposed patch
To: eliz AT is DOT elta DOT co DOT il
Date: Fri, 11 Jan 2002 12:15:12 -0600 (CST)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <557-Fri11Jan2002200216+0200-eliz@is.elta.co.il> from "Eli Zaretskii" at Jan 11, 2002 08:02:16 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> > > Maybe just put some impossible number, like -1 or something, instead
> > > of the handles in those FILE objects which are supposed to be
> > > preconnected.
> > 
> > This was my first thought, then I wondered if ANSI or POSIX had anything
> > to say about it - and if so what we wanted to do about it.
> 
> You mean that ANSI/Posix might require that stdin/stdout/stderr be
> always valid and ready to use?

That was a thought, yes.  Standards do help so we don't have to make it
all up as we go along :-)

> I don't know if they require this.  Can someone look?

Even if they require it doesn't mean we have to worry about it in the
pathological cases - but it was worth asking before coding.

Unless the standards require it *AND* we get a strong consensus that
we need to handle a pathological case of parent closing 0..2 handles,
I'd say just make them -1 to cause failures.