From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28022 invoked by alias); 26 Jul 2008 17:26:28 -0000 Received: (qmail 28012 invoked by uid 22791); 26 Jul 2008 17:26:27 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 26 Jul 2008 17:26:10 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m6QHPoEP001053; Sat, 26 Jul 2008 13:25:50 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m6QHPn2h017871; Sat, 26 Jul 2008 13:25:49 -0400 Received: from opsy.redhat.com (vpn-10-41.bos.redhat.com [10.16.10.41]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m6QHPnHK010329; Sat, 26 Jul 2008 13:25:49 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id AF86C37824B; Sat, 26 Jul 2008 11:25:48 -0600 (MDT) To: Eli Zaretskii Cc: Daniel Jacobowitz , bauerman@br.ibm.com, gdb-patches@sourceware.org Subject: Re: [RFA][patch 1/9] Yet another respin of the patch with initial Python support References: <20080615181833.uxmo25mg0kko40kw@imap.linux.ibm.com> <1216107418.14956.27.camel@localhost.localdomain> <1216245620.12209.18.camel@localhost.localdomain> <20080718195010.GA14356@caradoc.them.org> <1216653969.31797.6.camel@localhost.localdomain> <20080726134252.GA6077@caradoc.them.org> <20080726144138.GA9711@caradoc.them.org> From: Tom Tromey Reply-To: Tom Tromey X-Attribution: Tom Date: Sat, 26 Jul 2008 17:26:00 -0000 In-Reply-To: (Eli Zaretskii's message of "Sat\, 26 Jul 2008 20\:05\:31 +0300") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) 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: 2008-07/txt/msg00483.txt.bz2 >>>>> "Eli" == Eli Zaretskii writes: Eli> So are you saying that adding Python will enable features that are Eli> beyond user-defined commands (a.k.a. scripting)? If so, what are Eli> those features? The python programmer will be able to access nearly everything. We already have (on the branch) representations for threads, breakpoints, commands, internal functions (a new feature), blocks, frames, symbols, symbol tables, and values. We'll add more, too (at least types) -- but we're going through a round of cleanup-and-submit first. >> For example, we can pass a value or type and get back a friendlier >> display value or type; the long-requested C++/STL pretty-printing >> support. Eli> Maybe I'm missing something, because I don't see how this is different Eli> from what we have now. For example, the .gdbinit file distributed Eli> with Emacs already pretty-prints Emacs Lisp data types, as do the Eli> various GDB extensions for printing Qt data types that float around. Eli> They are all written in the current scripting CLI language. How will Eli> Python be different in this department? It will be integrated into "print" and will work with MI as well. Lots of projects distribute .gdbinit-style files like this. They all are lacking in various ways, due to shortcomings of gdb's command language. The Python approach will fix all of this. Pretty-printing is just one feature though. I want to push things much farther. Tom