From: Corinna Vinschen <vinschen@redhat.com>
To: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: [RFA/libiberty] Darwin has case-insensitive filesystems
Date: Wed, 15 Jun 2011 11:07:00 -0000 [thread overview]
Message-ID: <20110615105913.GA11991@calimero.vinschen.de> (raw)
In-Reply-To: <Pine.LNX.4.64.1106151043160.16094@digraph.polyomino.org.uk>
On Jun 15 10:45, Joseph S. Myers wrote:
> On Wed, 15 Jun 2011, Corinna Vinschen wrote:
>
> > these functions be replaced with multibyte-aware versions? Along the
> > same lines, the entire set of safe-ctype functions only work for ASCII
> > and EBCDIC...
>
> That's the whole point of safe-ctype: that code that is processing things
> such as C source code whose semantics do not depend on the host locale can
> examine character properties in a locale-independent way. Where C source
> code has multibyte characters, the correct handling depends in detail on
> the version of C and cannot be done by generic code.
Ok, I see.
Just in this specific case it's about filenames, not C source. I don't
think it makes sense to restrict filenames to ASCII or EBCDIC chars.
Corinna
--
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat
next prev parent reply other threads:[~2011-06-15 10:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 21:57 Joel Brobecker
2011-06-14 22:02 ` DJ Delorie
2011-07-01 17:58 ` Joel Brobecker
2011-06-14 22:06 ` Andrew Pinski
2011-06-14 22:13 ` DJ Delorie
2011-06-15 4:25 ` Tristan Gingold
2011-06-15 8:14 ` Joel Brobecker
2011-06-15 9:30 ` Corinna Vinschen
2011-06-15 10:44 ` Mark Kettenis
2011-06-15 10:55 ` Corinna Vinschen
2011-06-15 11:00 ` Pedro Alves
2011-06-15 11:26 ` Robert Dewar
2011-06-15 17:47 ` Eli Zaretskii
2011-06-15 10:59 ` Joseph S. Myers
2011-06-15 11:07 ` Corinna Vinschen [this message]
2011-06-15 17:35 ` Eli Zaretskii
2011-06-15 21:11 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110615105913.GA11991@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).