From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14322 invoked by alias); 21 Sep 2010 21:48:13 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 14310 invoked by uid 22791); 21 Sep 2010 21:48:13 -0000 X-SWARE-Spam-Status: No, hits=-6.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org From: Tom Tromey To: Matt Rice Cc: Oguz Kayral , Phil Muldoon , archer@sourceware.org Subject: Re: Python inferior control References: <4C655CA0.8010205@redhat.com> Date: Tue, 21 Sep 2010 21:48:00 -0000 In-Reply-To: (Matt Rice's message of "Mon, 20 Sep 2010 09:13:17 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2010-q3/txt/msg00207.txt.bz2 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