From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23368 invoked by alias); 26 Mar 2008 18:13:03 -0000 Received: (qmail 23359 invoked by uid 22791); 26 Mar 2008 18:13:03 -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; Wed, 26 Mar 2008 18:12:44 +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 m2QICYLZ012460; Wed, 26 Mar 2008 14:12:34 -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 m2QICXPx008817; Wed, 26 Mar 2008 14:12:33 -0400 Received: from opsy.redhat.com (vpn-248-165.boston.redhat.com [10.13.248.165]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m2QICXR2021778; Wed, 26 Mar 2008 14:12:33 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 8DBD73780C2; Wed, 26 Mar 2008 11:16:37 -0600 (MDT) To: Doug Evans Cc: Thiago Jung Bauermann , gdb ml Subject: Re: repo to work on python scripting support References: <1205538908.6643.138.camel@localhost.localdomain> <1206369478.29533.15.camel@localhost.localdomain> <20080326180455.GA22644@caradoc.them.org> From: Tom Tromey Reply-To: Tom Tromey X-Attribution: Tom Date: Wed, 26 Mar 2008 18:25:00 -0000 In-Reply-To: <20080326180455.GA22644@caradoc.them.org> (Daniel Jacobowitz's message of "Wed\, 26 Mar 2008 14\:04\:55 -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-03/txt/msg00244.txt.bz2 >>>>> "Daniel" == Daniel Jacobowitz writes: >> OOC, Would there be an intent to not disallow dynamically loaded C/C++ >> instead of Python for $(foo)? [Emphasis on OOC.] Daniel> My plan on this, to date, has been to insist on use of the Python Daniel> interface for marshalling and unmarshalling. This keeps the interface Daniel> explicit. Interesting -- since I just said the opposite :-) Are you concerned about the parsing problem for C-defined functions? We could push the parsing-style declarations down to the C level to solve that. I did want to say to Doug, but forgot -- is this something you're actually interested in? AFAIK you can't load gdb commands written in C or C++, so it would be a bit odd to add that feature just for these functions. Not that this matters hugely. And dynamically loading commands might also be useful. Daniel> print $(py "this is a python \"program\"") I was thinking some functions could ask for an uninterpreted string. print $(py do something in python) I'm not wedded to it. Tom