This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: fnmatch and invalid multibyte characters

From: Andreas Schwab <schwab at suse dot de>
To: Ulrich Drepper <drepper at redhat dot com>
Cc: libc-hacker at sources dot redhat dot com
Date: Fri, 29 Nov 2002 10:58:43 +0100
Subject: Re: fnmatch and invalid multibyte characters
References: <jevg2h4wl5.fsf@sykes.suse.de> <3DE660FC.6030403@redhat.com>

Ulrich Drepper <drepper@redhat.com> writes:

|> Andreas Schwab wrote:
|> > When fnmatch detects an invalid multibyte character it should fall back to
|> > single byte matching, so that "*" has a chance to match such a string.
|> 
|> And why is this better or more correct?

Just because the name contains some invalid multibyte characters does not
mean the file does not exist.

|> Is there existing practice?

The version of glob distributed with bash 2.05b does the same.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

References:
- fnmatch and invalid multibyte characters
  - From: Andreas Schwab
- Re: fnmatch and invalid multibyte characters
  - From: Ulrich Drepper

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]