From: Tristan Gingold <gingold@adacore.com>
To: DJ Delorie <dj@redhat.com>
Cc: Andrew Pinski <pinskia@gmail.com>,
Joel Brobecker <brobecker@adacore.com>,
"gcc-patches@gcc.gnu.org Patches" <gcc-patches@gcc.gnu.org>
Subject: Re: [RFA/libiberty] Darwin has case-insensitive filesystems
Date: Wed, 15 Jun 2011 04:25:00 -0000 [thread overview]
Message-ID: <F6F17782-2F53-4312-A090-0A0E29FD9430@adacore.com> (raw)
In-Reply-To: <201106142201.p5EM1vOd006127@greed.delorie.com>
On Jun 15, 2011, at 12:01 AM, DJ Delorie wrote:
>
>> This is wrong as not all FSs are case insensitive. In fact HFS+ can
>> be case sensitive too. I think you need better check than just
>> saying all Darwin is case insensitive. This is just like using
>> FAT32 on Linux. In fact I think HAVE_DOS_BASED_FILE_SYSTEM is
>> incorrect also for NTFS as it can also be case sensitive.
>
> There's a difference between case preserving and case sensitive,
> though, and we really don't have a portable way to detect
> case-sensitivity on a per-directory basis, sow how can we do better?
Seconded.
I have mixed feelings about this issue.
Handling HFS as case insensitive might not be user friendly, but on the other hand
it might be boring for developers working on a case sensitive HFS with two files that
differs only in case.
We can do something better using pathconf(2) with the _PC_CASE_SENSITIVE, but this would
result in an API change and maybe performance issue.
Tristan.
next prev parent reply other threads:[~2011-06-15 2:54 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 [this message]
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
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=F6F17782-2F53-4312-A090-0A0E29FD9430@adacore.com \
--to=gingold@adacore.com \
--cc=brobecker@adacore.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).