From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7124 invoked by alias); 13 Sep 2002 19:11:52 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 7117 invoked from network); 13 Sep 2002 19:11:52 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 13 Sep 2002 19:11:52 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu-dmz.redhat.com [172.16.52.200]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id g8DIt9w31270 for ; Fri, 13 Sep 2002 14:55:09 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g8DJBld23194; Fri, 13 Sep 2002 15:11:47 -0400 Received: from romulus.sfbay.redhat.com (remus.sfbay.redhat.com [172.16.27.252]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id g8DJBkC12527; Fri, 13 Sep 2002 12:11:46 -0700 Received: (from kev@localhost) by romulus.sfbay.redhat.com (8.11.6/8.11.6) id g8DJBgT19190; Fri, 13 Sep 2002 12:11:42 -0700 Date: Fri, 13 Sep 2002 12:11:00 -0000 From: Kevin Buettner Message-Id: <1020913191142.ZM19189@localhost.localdomain> In-Reply-To: Andrew Cagney "Re: [PATCH RFC] Character set support" (Sep 13, 2:42pm) References: <1020913003056.ZM15701@localhost.localdomain> <20020913004205.GB19479@nevyn.them.org> <20020913140312.GA10942@nevyn.them.org> <20020913173351.GA25544@nevyn.them.org> <3D823193.3020708@ges.redhat.com> To: Andrew Cagney , Daniel Jacobowitz Subject: Re: [PATCH RFC] Character set support Cc: Jim Blandy , gdb-patches@sources.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-09/txt/msg00260.txt.bz2 On Sep 13, 2:42pm, Andrew Cagney wrote: > > On Fri, Sep 13, 2002 at 12:02:29PM -0500, Jim Blandy wrote: > > > >> Daniel Jacobowitz writes: > > > >> > I'm not suggesting reading wchar_t's from the target; that's not > >> > terribly useful a thing to do. You _want_ the host wchar_t. It is > >> > a host type capable of holding a wide character; the type changes > >> > based on platform and on whether or not the platform actually has > >> > wide character support. > > > >> If you're suggesting using the host's wchar_t to hold characters after > >> conversion from the target charset to the host charset, then I'm with > >> you. > >> > >> If you're suggesting using the host's wchar_t to hold character values > >> that have been read from the target, but not yet converted to the > >> host's charset, then I really disagree. The target's wchar_t could be > >> 32 bits, while the host's might be 16 bits. > > > > Precisely. I was suggesting using host wchar_t after conversion to > > host format. > > Sounds like we need a WCHAREST :-) Yes, or something equivalent. What I'd like to determine is whether Daniel thinks that the notion of a wchar_t *must* be added to Jim's work before the patch can go in. (IMO, the wchar_t changes should be done as an incremental improvement.) Kevin