From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15356 invoked by alias); 14 Apr 2006 22:18:55 -0000 Received: (qmail 15346 invoked by uid 22791); 14 Apr 2006 22:18:54 -0000 X-Spam-Check-By: sourceware.org Received: from xproxy.gmail.com (HELO xproxy.gmail.com) (66.249.82.195) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 14 Apr 2006 22:18:53 +0000 Received: by xproxy.gmail.com with SMTP id h29so90618wxd for ; Fri, 14 Apr 2006 15:18:51 -0700 (PDT) Received: by 10.70.124.7 with SMTP id w7mr1052392wxc; Fri, 14 Apr 2006 15:18:50 -0700 (PDT) Received: by 10.70.125.5 with HTTP; Fri, 14 Apr 2006 15:18:50 -0700 (PDT) Message-ID: <8f2776cb0604141518g19e09431i404dccbe77262175@mail.gmail.com> Date: Sun, 16 Apr 2006 11:39:00 -0000 From: "Jim Blandy" To: "Jim Blandy" , "Eli Zaretskii" , ghost@cs.msu.su, gdb@sources.redhat.com Subject: Re: printing wchar_t* In-Reply-To: <20060414202720.GA23182@nevyn.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200604141257.41690.ghost@cs.msu.su> <200604141837.26618.ghost@cs.msu.su> <8f2776cb0604141053v73e512e3o2d1c9086312316bd@mail.gmail.com> <8f2776cb0604141216m216ba87ch529180cd079ce971@mail.gmail.com> <20060414202720.GA23182@nevyn.them.org> 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/msg00214.txt.bz2 As far as conveying strings accurately to GUI's via MI is concerned: It's fine to improve the way MI conveys data to the front end. It seems to me we still need to do things like repetition elimination and length limiting, but that syntax should certainly be designed to make the front ends' life easier. I'm not so sure about GDB doing character set conversion. I think I'd rather see GDB concentrate on accurately and safely conveying target code points to the front end, and make the front end responsible for displaying it. If the front end hasn't asked GDB to "print" the value in GDB's own way, then the front end has accepted responsibility for presentation, it seems to me.