From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24790 invoked by alias); 15 Jun 2011 10:59:53 -0000 Received: (qmail 24177 invoked by uid 22791); 15 Jun 2011 10:59:32 -0000 X-Spam-Check-By: sourceware.org Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.83/v0.83-20-g38e4449) with ESMTP; Wed, 15 Jun 2011 10:59:15 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 2AD472CAFA6; Wed, 15 Jun 2011 12:59:13 +0200 (CEST) Date: Wed, 15 Jun 2011 10:59:00 -0000 From: Corinna Vinschen To: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org Subject: Re: [RFA/libiberty] Darwin has case-insensitive filesystems Message-ID: <20110615105913.GA11991@calimero.vinschen.de> Reply-To: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org Mail-Followup-To: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org References: <1308087182-26577-1-git-send-email-brobecker@adacore.com> <201106142201.p5EM1vOd006127@greed.delorie.com> <20110615082236.GP12140@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-06/txt/msg00213.txt.bz2 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