From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10110121500.AA14347@clio.rice.edu>
Subject: Re: W2K/XP fncase [was Re: New perl package]
To: eliz AT is DOT elta DOT co DOT il
Date: Fri, 12 Oct 2001 10:00:35 -0500 (CDT)
Cc: djgpp-workers AT delorie DOT com, tim DOT van DOT holder AT pandora DOT be, acottrel AT ihug DOT com DOT au
In-Reply-To: <2561-Fri12Oct2001083139+0200-eliz@is.elta.co.il> from "Eli Zaretskii" at Oct 12, 2001 08:31:39 AM
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

> > So, since this function is hopeless on W2K/XP, ideas?  It would be much
> > faster to avoid all those useless interrupts ...
> 
> If we cannot find a way to fix this, I agree that we should simply
> bypass those calls on XP and behave as if FNCASE were set to y.

I would like to be compatible if possible.  It looks like this might be
possible to code directly (at least for 99% of the cases).  If lfn=y,
why not just use the first 8 chars before the period (in upper case)
and the first 3 after the period?  If the name didn't originally match
an 8.3 format we are going to fail matches against it anyway.  The only
special cases I see are files starting with period and some special
characters.