Sender: bcurrie AT tssc DOT co DOT nz
Message-ID: <3483625B.601C@tssc.co.nz>
Date: Tue, 02 Dec 1997 14:20:27 +1300
From: Bill Currie <bcurrie AT tssc DOT co DOT nz>
Organization: Telecommunication Systems Support Centre
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: Possible enhancements on v2.02
References: <199712020036 DOT TAA26549 AT delorie DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

DJ Delorie wrote:

> If we enable LFN during startup, it should ONLY be for finding the
> djgpp.env file.  Expanding wildcards with it is a bad idea, as long as
> the short names can still be used after we switch to LFN.

By this, do you mean: wildcard expansion is SFN only; or wildcard
expansion will be LFN iff LFN=y?  Your statement is a little ambiguous.

I'm bringing this up because the lfn driver I'm working on hides the SFN
of files that have LFNs (by default, this will be configurable). ie if
wildcards are expanded using the SFN and LFN is enabled, the program
won't be able to find the files that have been expanded.  Also, there is
the possiblity of other systems that work this way (though I don't know
of any).

However, I agree that if djgpp.env turns off LFN, wildcards should be
expanded using SFN.

Bill
-- 
Leave others their otherness