Date:	Mon, 1 May 2000 09:07:04 -0700
From:	Zack Weinberg <zack AT wolery DOT cumb DOT org>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc:	Laurynas Biveinis <lauras AT softhome DOT net>, gcc-patches AT gcc DOT gnu DOT org,
	djgpp-workers AT delorie DOT com
Subject:	Re: Minor DJGPP fixes
Message-ID:	<20000501090704.M11780@wolery.cumb.org>
References:	<390C769C DOT 812EAB7D AT softhome DOT net> <20000501000928 DOT J11780 AT wolery DOT cumb DOT org> <200005010837 DOT EAA00013 AT indy DOT delorie DOT com>
Mime-Version:	1.0
User-Agent:	Mutt/1.1.12i
In-Reply-To:	<200005010837.EAA00013@indy.delorie.com>; from eliz@delorie.com on Mon, May 01, 2000 at 04:37:09AM -0400
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

On Mon, May 01, 2000 at 04:37:09AM -0400, Eli Zaretskii wrote:
> > - fcntl() working is a characteristic of the _host_, not the target.
> > - You should determine if it works using an autoconf test.
> 
> Why didn't the original code use an Autoconf test, then?  I understand
> that it was added only recently.

Because I never dreamed that any system wouldn't support that
particular fcntl() operation.  It's been around since forever in
Unix.  I'm tempted to tell you to fix your library.

> > - If it doesn't work, you need to open the file in blocking mode, not
> >   just elide the fcntl(); otherwise the code reading the file will
> >   break. 
> 
> Could you please explain what does ``open in blocking mode'' mean?
> Isn't a normal default `open' good enough?  If not, why not?

I think this has been adequately explained elsewhere.

zw

- Raw text -