From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25878 invoked by alias); 15 Jun 2011 11:00:51 -0000 Received: (qmail 25864 invoked by uid 22791); 15 Jun 2011 11:00:50 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 15 Jun 2011 11:00:29 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 553632BB2CD; Wed, 15 Jun 2011 07:00:22 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1rmUTN95Q4S9; Wed, 15 Jun 2011 07:00:22 -0400 (EDT) Received: from [127.0.0.1] (kwai.gnat.com [205.232.38.4]) by rock.gnat.com (Postfix) with ESMTP id D57B82BB2CC; Wed, 15 Jun 2011 07:00:20 -0400 (EDT) Message-ID: <4DF8907F.5080807@adacore.com> Date: Wed, 15 Jun 2011 11:26:00 -0000 From: Robert Dewar User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Mark Kettenis CC: vinschen@redhat.com, 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 References: <1308087182-26577-1-git-send-email-brobecker@adacore.com> <201106142201.p5EM1vOd006127@greed.delorie.com> <20110615082236.GP12140@calimero.vinschen.de> <201106150958.p5F9wJ7x019158@glazunov.sibelius.xs4all.nl> In-Reply-To: <201106150958.p5F9wJ7x019158@glazunov.sibelius.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2011-06/txt/msg01148.txt.bz2 On 6/15/2011 5:58 AM, Mark Kettenis wrote: > Over my dead body. On a proper operating system filenames are > case-sensitive. Your suggestion would create spurious matches. Yes, we all know that Unix systems chose case sensitive, and are happy to have files differing only by case in the same directory. Obviously any proper software has to fully support such systems (if I was in the same mode as you and adding gratuitious flames to my comments, I would have preceded the word systems by brain-dead). > > Even on case-preserving filesystems I'd argue that treating them as > case-sensitive is still the right approach. Absolutely not, please don't visit your unix-borne predjudices on non-unix systems. There is nothing worse for Windows users than having to put up with silly decisions like this that visit unix nonsense (and it is nonsense in a windows environment) on windows software. > If that creates problems, > it means somebody was sloppy and didn't type the proper name of the > file The whole point in a system like Windows which is case preserving but not case sensitive is that you are NOT expected to type in the "proper" capitalization. In English, we recognize the words English and ENGLISH as equivalent, and windows users expect the same treatment. So the normal expectation in windows systems is that, yes, you can make nice capitalization like MyFile if you like, and it will be properly displayed. But any software that requires me to type MyFile rather than myfile is junk! > If you're still using an operating system with fully case-insensitive > filesystems, I feel very, very sorry for you. You are allowed to have this opinion, I feel the same about people who have to tolerate case-sensitive file systems, but I am quite happy with software for Unix systems fully behaving (I would agree that any software that EVER did case insensitive matching, as suggested earlier in this thread would be broken on Unix). But following your suggestion would be equally broken in Windows. > or some piece of code in the toolchain arbitrarily changed the > case of a filename. I don't mind punishing people for that. They > have to learn that on a proper operating system file names are > case-sensitive! This kind of unix arrogance leads to junk unusable software on windows. It's really important not to visit your unix predjudices on windows users. After all we feel the same way in return, I find Unix systems complete junk for many reasons, one of which is the very annoying case sensitive viewpoint, but I do not translate my feelings into silly suggestions for making software malfunction on Unix. You should not make this mistake in a reverse direction.