Sender: bcurrie AT tssc DOT co DOT nz
Message-ID: <34845ADC.481C@tssc.co.nz>
Date: Wed, 03 Dec 1997 08:00:44 +1300
From: Bill Currie <bcurrie AT tssc DOT co DOT nz>
Organization: Telecommunication Systems Support Centre
MIME-Version: 1.0
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC: djgpp-workers AT delorie DOT com
Subject: Re: Possible enhancements on v2.02
References: <Pine DOT SUN DOT 3 DOT 91 DOT 971202141858 DOT 11994B-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Eli Zaretskii wrote:
> 
> On Tue, 2 Dec 1997, Bill Currie wrote:
> 
> > 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).
> 
> *Bad* idea, IMHO.  This is NOT what Windows 9X does.  The LFN API
> calls work with both long and short names.  If you disable that, some
> pretty subtle bugs will surface.  I don't remember the exact examples
> right now, but I *know* there are some cases when this feature saves
> the day.

One example I can think of is when using the result of truename (7160).
I'm not sure if I've got all the bugs taken care of for this, but my lfn
driver will return the LFN form for the expanded path if the above
option is enabled.  That was the only problem caused by this option I
could think of. If you know/think of any others, please let me know.
IMHO, W95 screwed up. I've found the W95 method more trouble than it's
worth.  However, I realize that that not everyone agrees with me on this
and that's why I made it optional.

Bill
-- 
Leave others their otherness