delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2001/08/22/13:14:00

Date: Wed, 22 Aug 2001 20:11:25 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: sandmann AT clio DOT rice DOT edu
Message-Id: <8361-Wed22Aug2001201124+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
CC: djgpp-workers AT delorie DOT com
In-reply-to: <10108221623.AA18243@clio.rice.edu> (sandmann@clio.rice.edu)
Subject: Re: Fseek on STDIN problem on Win 2K
References: <10108221623 DOT AA18243 AT clio DOT rice DOT edu>
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

> From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
> Date: Wed, 22 Aug 2001 11:23:38 -0500 (CDT)
> 
> > > I don't know the answer to any of these questions - we'll have to
> > > write a lot of test programs.
> > 
> > I think we should.  lseek is too important.
> 
> Goal 1: Fix burning W2K issues to get the toolkit working on Win XP.
> Everything else is after this.  This is an *OLD* bug.

I agree in general, but I'm not sure this one is not a burning issue.
I don't think the fact it never surfaced before is significant (see my
other mail).  But I won't argue with you about the order in which you
are attacking problems.

What _are_ the burning issues that are left unsolved, btw?

> > > Here's a thought - I've used lseek/read/write on NT with DJGPP 
> > > somewhat frequently in the last several years without seeing this
> > > problem.  Let's assume for a second this is only seen on handles
> > > opened by NT for us, that have the weird "0" behavior.  If we 
> > > declared these as pipes (completely valid for NT, and a case we
> > > probably need to handle anyway) then no one seeks on STDIN and the
> > > problem goes away.
> > 
> > I'm not sure what exactly do you mean by ``declare these as pipes''.
> > Does this mean some changes in the library, or just documentation?
> 
> Library change.  We shouldn't be getting magic numbers on pipes.

How can we detect that a particular handle is a pipe?  Handle zero is
not special: some program could close it and open some file on it.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019