Date: Tue, 12 Jan 1999 11:24:57 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Laszlo Molnar <laszlo DOT molnar AT eth DOT ericsson DOT se>
cc: DJGPP Workers List <djgpp-workers AT delorie DOT com>
Subject: Re: djgpp 2.02 + perl + glob
In-Reply-To: <19990112094755.O29345@duna54>
Message-ID: <Pine.SUN.3.91.990112112109.15876Y-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com


On Tue, 12 Jan 1999, Laszlo Molnar wrote:

> The problem: when a new handle is
> allocated, it is not opened, but dup()-ed in djgpp 2.02.

Right.  This change was done to prevent fsext from failing when it 
exhausts the max count of handles determined by the FILES= directive.  
`dup' is not limited by FILES=, and so can go up to the maximum of 255 
handles that DOS allows.

> It would work
> perfectly if the file pointer would be set to 0, ie an lseek(..,0,0)
> should be added after dup() IMHO.

Can you elaborate why is this needed?  Is this something specific to the 
way Perl uses fsext, or do you think this is a general problem, and why?

Don't forget that lseek itself might be hooked by the fsext, btw.