From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16233 invoked by alias); 15 Jan 2009 21:18:26 -0000 Received: (qmail 16223 invoked by uid 22791); 15 Jan 2009 21:18:25 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 15 Jan 2009 21:17:49 +0000 Received: (qmail 8689 invoked from network); 15 Jan 2009 21:17:48 -0000 Received: from unknown (HELO digraph.polyomino.org.uk) (joseph@127.0.0.2) by mail.codesourcery.com with ESMTPA; 15 Jan 2009 21:17:48 -0000 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.68) (envelope-from ) id 1LNZb0-0001SN-PR; Thu, 15 Jan 2009 21:17:46 +0000 Date: Thu, 15 Jan 2009 21:18:00 -0000 From: "Joseph S. Myers" To: Tom Tromey cc: Julian Brown , gdb-patches@sourceware.org Subject: Re: [PATCH/WIP] C/C++ wchar_t/Unicode printing support In-Reply-To: Message-ID: References: <20090115202411.5f154657@rex.config> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: 2009-01/txt/msg00364.txt.bz2 On Thu, 15 Jan 2009, Tom Tromey wrote: > * Handles input and output of wide characters and strings, and also > the new C0X u"" and U"" syntax. (Of course, now C++0x has and C1x has accepted (not yet in a draft) a lot of further new string syntax that Jakub has implemented for GCC 4.5.) If you handle input of the new string syntax, do you also handle the interesting concatenation issues? "\xab" L"c" is a wide string with two characters, L'\xab' and L'c' (plus the trailing NUL); you do not interpret '\xab' as a member of the target narrow character set and convert to the target wide character set (nor do you interpret it as L"\xabc", with a single escape sequence), so you can't convert escape sequences to bytes of a string until after you know whether the final string is narrow or wide (or some other variant, in C++0x/C1x). -- Joseph S. Myers joseph@codesourcery.com