From: Tom Tromey <tromey@redhat.com>
To: Matt Rice <ratmice@gmail.com>
Cc: Oguz Kayral <oguzkayral@gmail.com>,
Phil Muldoon <pmuldoon@redhat.com>,
archer@sourceware.org
Subject: Re: Python inferior control
Date: Tue, 21 Sep 2010 21:48:00 -0000 [thread overview]
Message-ID: <m37hiedazv.fsf@fleche.redhat.com> (raw)
In-Reply-To: <AANLkTikE85MG4_Bp1ghPwqO7kEjvog0yVrxuznvH1uAF@mail.gmail.com> (Matt Rice's message of "Mon, 20 Sep 2010 09:13:17 -0700")
Matt> with the simplified event dictionary tromey describes, and the type
Matt> flag to go with it, you could just use a single stack/linked list to
Matt> push/pop all types of events onto,
Interesting idea.
Alternatively, we could have an "any_event" source. I suspect most
event receivers will only want to connect to a particular source.
Matt> is this stuff on a branch somewhere?
Just gsoc-kayral-python. I think that is rather old.
Phil prepared a RFC patch, but AFAIK that isn't committed anywhere.
Tom
next prev parent reply other threads:[~2010-09-21 21:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 14:54 Phil Muldoon
2010-08-13 19:49 ` Tom Tromey
2010-08-26 15:02 ` Oguz Kayral
2010-08-26 20:28 ` Tom Tromey
2010-09-20 16:13 ` Matt Rice
2010-09-21 21:48 ` Tom Tromey [this message]
2010-08-15 17:42 ` Richard Ward
2010-08-26 20:23 ` Tom Tromey
2010-08-25 16:10 ` Phil Muldoon
2010-12-01 18:58 ` sami wagiaalla
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=m37hiedazv.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=oguzkayral@gmail.com \
--cc=pmuldoon@redhat.com \
--cc=ratmice@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).