From: Tom Tromey <tromey@redhat.com>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [Python - doc] gdb.post_event description
Date: Wed, 19 Oct 2011 20:45:00 -0000 [thread overview]
Message-ID: <m3d3dsvi6q.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAPftXUKyqtj3_eEUstd52ioqjHk2hzNVfpeZDaEKD57Jy9xG3w@mail.gmail.com> (Kevin Pouget's message of "Tue, 18 Oct 2011 13:56:48 +0200")
>>>>> "Kevin" == Kevin Pouget <kevin.pouget@gmail.com> 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
prev parent reply other threads:[~2011-10-19 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 8:53 Kevin Pouget
2011-10-14 19:49 ` Tom Tromey
2011-10-18 13:32 ` Kevin Pouget
2011-10-18 13:58 ` Phil Muldoon
2011-10-19 20:45 ` Tom Tromey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3d3dsvi6q.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevin.pouget@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox