Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Corinna Vinschen <vinschen@redhat.com>
Cc: dj@redhat.com, pinskia@gmail.com, brobecker@adacore.com,
	gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: [RFA/libiberty] Darwin has case-insensitive filesystems
Date: Wed, 15 Jun 2011 17:29:00 -0000	[thread overview]
Message-ID: <8362o79f9j.fsf@gnu.org> (raw)
In-Reply-To: <20110615082236.GP12140@calimero.vinschen.de>

> Date: Wed, 15 Jun 2011 10:22:36 +0200
> From: Corinna Vinschen <vinschen@redhat.com>
> Cc: Andrew Pinski <pinskia@gmail.com>, brobecker@adacore.com,	gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
> 
> Talking about case-insensitive comparison, the filename_cmp and
> filename_ncmp functions don't work for multibyte codesets, only for
> singlebyte codesets.  Given that UTF-8 is standard nowadays, shouldn't
> these functions be replaced with multibyte-aware versions?

I agree, but if we go that way, shouldn't we support UTF-16, which is
used by the native Windows APIs?  Windows does not use UTF-8 for file
names.


  parent reply	other threads:[~2011-06-15 17:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 21:33 Joel Brobecker
2011-06-14 21:38 ` DJ Delorie
2011-07-01 17:58   ` Joel Brobecker
2011-06-14 21:57 ` Andrew Pinski
2011-06-14 22:02   ` DJ Delorie
2011-06-15  4:25     ` Joel Brobecker
2011-06-15  8:23     ` Corinna Vinschen
2011-06-15  9:59       ` Mark Kettenis
2011-06-15 10:45         ` Corinna Vinschen
2011-06-15 10:55           ` Pedro Alves
2011-06-15 11:00         ` Robert Dewar
2011-06-15 17:30           ` Eli Zaretskii
2011-06-15 10:46       ` Joseph S. Myers
2011-06-15 10:59         ` Corinna Vinschen
2011-06-15 17:29       ` Eli Zaretskii [this message]
2011-06-15 19:42         ` 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=8362o79f9j.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pinskia@gmail.com \
    --cc=vinschen@redhat.com \
    /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