From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18560 invoked by alias); 17 Jun 2008 20:38:23 -0000 Received: (qmail 18550 invoked by uid 22791); 17 Jun 2008 20:38:22 -0000 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 17 Jun 2008 20:38:05 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 6E8741EFA13; Tue, 17 Jun 2008 16:38:03 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id KZ7fmXRfUqPf; Tue, 17 Jun 2008 16:38:03 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 3A6881EFA07; Tue, 17 Jun 2008 16:38:03 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id DB49FE7ACD; Tue, 17 Jun 2008 16:37:41 -0400 (EDT) Date: Tue, 17 Jun 2008 22:20:00 -0000 From: Joel Brobecker To: Thiago Jung Bauermann Cc: Daniel Jacobowitz , Tom Tromey , gdb-patches@sourceware.org Subject: Re: [RFC][patch 3/9] export hooks mechanism to Python Message-ID: <20080617203741.GA3711@adacore.com> References: <20080615183110.xi9zc6qx2iokwwsg@imap.linux.ibm.com> <20080616014219.GA9913@caradoc.them.org> <20080617121342.k0o647casks4w4c4@imap.linux.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080617121342.k0o647casks4w4c4@imap.linux.ibm.com> User-Agent: Mutt/1.4.2.2i 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-06/txt/msg00325.txt.bz2 > Observers look like a useful feature in GDB to be used by scripts, > IMHO we should think about ways to make it available to python, and consider > turning it into a stable exported interface... Exposing some events to Python sounds pretty reasonable, but I also prefer if we did not expose the observers directly, for the reasons that Daniel explained. The event at the Python would be very well defined and (hopefully) stable while we are free to modify the observers. -- Joel