From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-18584-listarch-gdb-patches=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 29424 invoked by alias); 13 Sep 2002 18:42:31 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 29415 invoked from network); 13 Sep 2002 18:42:30 -0000
Received: from unknown (HELO localhost.redhat.com) (216.138.202.10)
  by sources.redhat.com with SMTP; 13 Sep 2002 18:42:30 -0000
Received: from ges.redhat.com (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id CCBEC3C96; Fri, 13 Sep 2002 14:42:27 -0400 (EDT)
Message-ID: <3D823193.3020708@ges.redhat.com>
Date: Fri, 13 Sep 2002 11:42:00 -0000
From: Andrew Cagney <ac131313@ges.redhat.com>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Jim Blandy <jimb@redhat.com>, Kevin Buettner <kevinb@redhat.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFC] Character set support
References: <1020913003056.ZM15701@localhost.localdomain> <20020913004205.GB19479@nevyn.them.org> <vt2n0qmwpm9.fsf@zenia.red-bean.com> <20020913140312.GA10942@nevyn.them.org> <vt2n0qlvn4q.fsf@zenia.red-bean.com> <20020913173351.GA25544@nevyn.them.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2002-09/txt/msg00258.txt.bz2

> On Fri, Sep 13, 2002 at 12:02:29PM -0500, Jim Blandy wrote:
> 
>> 
>> Daniel Jacobowitz <drow@mvista.com> 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 :-)

Andrew