From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16496 invoked by alias); 14 Apr 2006 14:29:54 -0000 Received: (qmail 16487 invoked by uid 22791); 14 Apr 2006 14:29:53 -0000 X-Spam-Check-By: sourceware.org Received: from nitzan.inter.net.il (HELO nitzan.inter.net.il) (192.114.186.20) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 14 Apr 2006 14:29:50 +0000 Received: from HOME-C4E4A596F7 (IGLD-83-130-214-179.inter.net.il [83.130.214.179]) by nitzan.inter.net.il (MOS 3.7.3-GA) with ESMTP id DDG09412 (AUTH halo1); Fri, 14 Apr 2006 17:29:46 +0300 (IDT) Date: Fri, 14 Apr 2006 14:47:00 -0000 Message-Id: From: Eli Zaretskii To: Paul Koning CC: ghost@cs.msu.su, gdb@sources.redhat.com In-reply-to: <17471.42725.651176.368871@gargle.gargle.HOWL> (message from Paul Koning on Fri, 14 Apr 2006 09:43:01 -0400) Subject: Re: printing wchar_t* Reply-to: Eli Zaretskii References: <17471.42725.651176.368871@gargle.gargle.HOWL> 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/msg00192.txt.bz2 > Date: Fri, 14 Apr 2006 09:43:01 -0400 > From: Paul Koning > Cc: ghost@cs.msu.su, gdb@sources.redhat.com > > If you have 16 bit wide chars, it seems possible that those might > contain UTF-16 encoding of full (beyond BMP) Unicode characters. You could use wchar_t arrays for that, but then not every array element will be a full character, and you will not be able to access individual characters by their positional index. In other words, in this case each element of the wchar_t array is no longer a ``wide character'', but one of the few shorts that encode a character. If we want to support wchar_t arrays that store UTF-16, we will need to add a feature to GDB to convert UTF-16 to the full UCS-4 codepoints, and output those. Alternatively, the FE will have to support display of UTF-16 encoded characters.