From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21138 invoked by alias); 23 Jun 2008 15:16:11 -0000 Received: (qmail 21130 invoked by uid 22791); 23 Jun 2008 15:16:11 -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; Mon, 23 Jun 2008 15:15:53 +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 m5NFFX0E017255; Mon, 23 Jun 2008 11:15:33 -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 m5NFFWhj006172; Mon, 23 Jun 2008 11:15:33 -0400 Received: from opsy.redhat.com (vpn-10-3.bos.redhat.com [10.16.10.3]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m5NFFW93013044; Mon, 23 Jun 2008 11:15:32 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 1B66B378176; Mon, 23 Jun 2008 09:15:32 -0600 (MDT) To: Joel Brobecker Cc: gdb@sourceware.org Subject: Re: GDB Focus Group at the 2008 GCC Summit References: <20080619190942.GA3744@adacore.com> From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom Date: Mon, 23 Jun 2008 15:16:00 -0000 In-Reply-To: <20080619190942.GA3744@adacore.com> (Joel Brobecker's message of "Thu\, 19 Jun 2008 15\:09\:42 -0400") 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-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-06/txt/msg00215.txt.bz2 >>>>> "Joel" == Joel Brobecker writes: Joel> | * Calling python function from the CLI: Joel> | Several possible syntaxes: Joel> | $(function-name arguments) Joel> | $function_name (arguments) Joel> | And also, should be treat the arguments as a simple string, Joel> | or should we treat each argument as an expression? Joel> | We reached a consensus and Tom to send it to the gdb list. Our consensus was to use the function-like syntax (second example above) and to parse the arguments as expressions. This does mean there is a namespace issue, but we reasoned that we could make all the standard functions have a "gdb_" prefix or something like that. I'm about 80% done with implementing this. I'm using an approach suggested by Daniel, which is to add a new "convenience function" type. Also we agreed that new Python classes should use implicit Python functions when it makes sense -- that is, use __str__ rather than an explicit to_string. Tom