X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f Date: Sat, 29 Dec 2001 22:40:24 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: wojciech DOT galazka AT polkomtel DOT com DOT pl Message-Id: <2427-Sat29Dec2001224024+0200-eliz@is.elta.co.il> X-Mailer: emacs 21.1.50 (via feedmail 8 I) and Blat ver 1.8.9 CC: djgpp-workers AT delorie DOT com In-reply-to: <250B3114DA16D511B82C00E0094005F8055AC80B@MSGWAW11> (message from =?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?= on Sat, 29 Dec 2001 20:35:26 +0100) Subject: Re: lfn from scratch... References: <250B3114DA16D511B82C00E0094005F8055AC80B AT MSGWAW11> 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 > From: =?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?= > Date: Sat, 29 Dec 2001 20:35:26 +0100 > > > 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 ? Some of the library functions do call _use_lfn with a non-NULL file name argument. > > 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. Perhaps; but that, too, does not require any handler, just a replacement in a separate library.