From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13543 invoked by alias); 19 Oct 2011 20:30:09 -0000 Received: (qmail 13371 invoked by uid 22791); 19 Oct 2011 20:30:00 -0000 X-SWARE-Spam-Status: No, hits=-7.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS 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; Wed, 19 Oct 2011 20:29:36 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p9JKTZG2012693 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 19 Oct 2011 16:29:35 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p9JKTZB9010000; Wed, 19 Oct 2011 16:29:35 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id p9JKTYpi013640; Wed, 19 Oct 2011 16:29:34 -0400 From: Tom Tromey To: Kevin Pouget Cc: gdb-patches@sourceware.org Subject: Re: [Python - doc] gdb.post_event description References: Date: Wed, 19 Oct 2011 20:45:00 -0000 In-Reply-To: (Kevin Pouget's message of "Tue, 18 Oct 2011 13:56:48 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (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: 2011-10/txt/msg00538.txt.bz2 >>>>> "Kevin" == Kevin Pouget writes: Kevin> but I think that the notion of "event" is quite vague here, for Kevin> instance we've got Python events, which are totally unrelated to Kevin> "post_event" (as far as I understood); and internally there are Kevin> inferior events. Kevin> (Actually, with that knowledge, I expected 'post_event' events to be Kevin> processed more often). Kevin> So I think it's important to state when the callback will be Kevin> triggered, give the prompt as an example, and mentioned that more Kevin> event processing points might be added in the next releases Kevin> What do you think about it? Yeah, the choice of name for 'gdb.post_event' was unfortunate. I think a change to the docs making it clear that post_event and the event mechanism are unrelated would be good. I wouldn't even mind if it mentioned the CLI or accepting input or something, as long as it also mentioned that we may expand it to run at other times as well in the future. Tom