From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18317 invoked by alias); 25 Mar 2008 11:45:48 -0000 Received: (qmail 18304 invoked by uid 22791); 25 Mar 2008 11:45:47 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 25 Mar 2008 11:45:24 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id C2A5398140; Tue, 25 Mar 2008 11:45:22 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 922089810C; Tue, 25 Mar 2008 11:45:22 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1Je7ai-0005XO-M0; Tue, 25 Mar 2008 07:45:20 -0400 Date: Tue, 25 Mar 2008 13:53:00 -0000 From: Daniel Jacobowitz To: Tom Tromey Cc: Thiago Jung Bauermann , gdb ml Subject: Re: repo to work on python scripting support Message-ID: <20080325114520.GA21688@caradoc.them.org> Mail-Followup-To: Tom Tromey , Thiago Jung Bauermann , gdb ml References: <1205538908.6643.138.camel@localhost.localdomain> <1206369478.29533.15.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes 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-03/txt/msg00217.txt.bz2 On Mon, Mar 24, 2008 at 11:32:16PM -0600, Tom Tromey wrote: > I've been thinking... maybe we do want $(...) to allow things other > than Python commands. Or, more precisely, maybe we want to let Python > code register a function by name for use in $(...). The Python > function would get the uninterpreted string argument for processing. I was thinking about this unrelatedly last night and I agree, we should register the arguments independently. I'm not so sure about quoting decisions for the arguments yet, though. What I don't want to do is end up with the GDB CLI again, where everyone who adds a command picks a different way to quote the arguments. Maybe we can handle this the same way that I have been speculating about handling CLI commands: register a "prototype" of the function? For example, you could register: $(strcmp expression, "foo") as "EXPRESSION, EXPRESSION". Other functions might not have the comma if the preceeding argument was not an EXPRESSION. -- Daniel Jacobowitz CodeSourcery