From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17539 invoked by alias); 28 Jul 2010 17:31:43 -0000 Received: (qmail 17531 invoked by uid 22791); 28 Jul 2010 17:31:42 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 28 Jul 2010 17:31:35 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 255AB2BAC1C; Wed, 28 Jul 2010 13:31:34 -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 nZlVaQB8ZcU2; Wed, 28 Jul 2010 13:31:34 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id DEDE82BAC18; Wed, 28 Jul 2010 13:31:33 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 73FA9F58FA; Wed, 28 Jul 2010 10:31:28 -0700 (PDT) Date: Wed, 28 Jul 2010 17:31:00 -0000 From: Joel Brobecker To: Phil Muldoon Cc: gdb-patches ml Subject: Re: [patch] Implement post_event for Python scripts. Message-ID: <20100728173128.GM13267@adacore.com> References: <4C45F0B0.5000903@redhat.com> <20100727162956.GG13267@adacore.com> <4C503BFE.8090608@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C503BFE.8090608@redhat.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2010-07/txt/msg00492.txt.bz2 > Providing an example of a multi-threaded python script using > post_event would be too complex for the manual (I'm not sure that was > what you wanted anyway). I provided a small example that shows usage. > Is this okay? I'm just trying to figure out how this feature can be useful, and in particular when the callbacks are triggered. Perhaps, rather than an example, what we need is a section that describes the event loop and when it is queried. We can then make a reference to that section. It would have been nice if we could have had a small example that actually did something cool, but if the concepts are clear enough, the user should be able to figure out what it can use it for. -- Joel