From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32591 invoked by alias); 9 Jul 2012 21:10:04 -0000 Received: (qmail 32579 invoked by uid 22791); 9 Jul 2012 21:10:04 -0000 X-SWARE-Spam-Status: No, hits=-6.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 09 Jul 2012 21:09:45 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q69L9gOc016342 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Jul 2012 17:09:42 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q69L9evW010927 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 9 Jul 2012 17:09:41 -0400 From: Tom Tromey To: Tom Emerson Cc: Ludovic =?utf-8?Q?Court=C3=A8s?= , gdb-patches@sourceware.org Subject: Re: GDB and Guile References: <87y5msdhzz.fsf@gnu.org> Date: Mon, 09 Jul 2012 21:10:00 -0000 In-Reply-To: (Tom Emerson's message of "Mon, 9 Jul 2012 16:35:18 -0400") Message-ID: <87bojok5ez.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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: 2012-07/txt/msg00118.txt.bz2 Tom> Parity with the Python functionality is obviously the first order Tom> of business, which in turn speaks to generalizing the interface Tom> between GDB and Python so that it is more (extension language) Tom> neutral. It depends on what exactly you mean here, but to I don't think we want any kind of generic extension API. I think the way that gdb is exposed to Python has to be ad hoc, and for good reason -- we want control over API evolution as seen by Python to a degree that we actively don't want internally. If you can give more details on what you plan I can give better feedback. I just didn't want you to set off down a bad path. Tom