Date: Wed, 1 Mar 2000 13:40:47 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Mariano Alvarez =?iso-8859-1?Q?Fern=E1ndez?= <malfer AT teleline DOT es>,
        djgpp-workers AT delorie DOT com
Subject: Re: short file names when using LFN
In-Reply-To: <Pine.SUN.3.91.1000301121652.12637M-100000@is>
Message-ID: <Pine.SUN.3.91.1000301133831.13388A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 1 Mar 2000, I wrote:

> 
> On Tue, 29 Feb 2000, Mariano Alvarez =?iso-8859-1?Q?Fern=E1ndez?= wrote:
> 
> >     Searching the Ralph Brown I found the interrupt to get the short
> > file name when using LFN. Here is the routine. Really I d'ont know very
> > much about the DJGPP internals, so I made the routine modifying the
> > "_gen_short_filename" one.
> 
> _lfn_gen_short_filename is not meant to do this, it has a different
> (and very important) functionality.

That was not clear enough, I think.  What I meant to say is that 
_lfn_gen_short_filename is used by many library functions for some subtle 
aspects of long-filename handling, such as the automatic downcasing of 
file names.  So replacing that function in the library would be a very 
bad idea indeed.