From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27051 invoked by alias); 14 Apr 2006 13:07:36 -0000 Received: (qmail 26987 invoked by uid 22791); 14 Apr 2006 13:07:35 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Fri, 14 Apr 2006 13:07:32 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FUO1K-0003Us-16; Fri, 14 Apr 2006 09:07:30 -0400 Date: Fri, 14 Apr 2006 13:17:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: Vladimir Prus , gdb@sources.redhat.com Subject: Re: printing wchar_t* Message-ID: <20060414130729.GB12955@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , Vladimir Prus , gdb@sources.redhat.com References: <200604141246.58094.ghost@cs.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-04/txt/msg00182.txt.bz2 On Fri, Apr 14, 2006 at 03:55:49PM +0300, Eli Zaretskii wrote: > Anyway, UTF-16 is a variable-length encoding, so wchar_t is not it. There's a rant about this in the glibc manual I was just reading... In fact, on many platforms, wchar_t is only 16-bit. How exactly you handle UTF-8 or UCS-4 input in this case, I don't really understand. -- Daniel Jacobowitz CodeSourcery