X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Message-ID: <250B3114DA16D511B82C00E0094005F8055AC80B@MSGWAW11>
From: =?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?= <wojciech DOT galazka AT polkomtel DOT com DOT pl>
To: "'Eli Zaretskii'" <eliz AT is DOT elta DOT co DOT il>
Cc: djgpp-workers AT delorie DOT com
Subject: RE: lfn from scratch...
Date: Sat, 29 Dec 2001 20:35:26 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-2"
Reply-To: djgpp-workers AT delorie DOT com



> From: Eli Zaretskii [mailto:eliz AT is DOT elta DOT co DOT il]

> This is not an application-level issue: if some drives don't support
> the LFN API, _all_ applications on that system will have to modify
> the way they use the result of _USE_LFN.

Either modify or assume that no drive supports LFN API
because the default drive does not support it and libc calls _use_lfn(0) to 
check for LFN API support
Or I'm wrong there ?
 
> Since this applies to all programs, simply replacing _use_lfn with a
> custom version will do what you want.  So I don't see a reason to
> invent an application-level feature like the one you suggest.
> 

It's easier to put a custom version of _use_lfn in a separate library 
than to modify libc itself.