From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10325 invoked by alias); 25 Apr 2005 16:08:37 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 10017 invoked from network); 25 Apr 2005 16:08:27 -0000 Received: from unknown (205.217.158.180) by sourceware.org with QMTP; 25 Apr 2005 16:08:27 -0000 Received: (qmail 23588 invoked by uid 10); 25 Apr 2005 16:08:26 -0000 Received: (qmail 18664 invoked by uid 500); 25 Apr 2005 16:08:16 -0000 To: "M.M. Kettenis" Cc: Christopher Faylor , Mark Mitchell , gdb-patches@sources.redhat.com Subject: Re: PATCH: Support Windows in event-loop.c References: <7320615710191969@webhare> From: Ian Lance Taylor Date: Mon, 25 Apr 2005 16:08:00 -0000 In-Reply-To: <7320615710191969@webhare> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2005-04/txt/msg00316.txt.bz2 > > Ok... So, is it acceptable to include a console-only implementation in > > event-loop.c? I would think that it wasn't. > > That seems to suggest that some kind of generic select or poll > > implementation needs to be developed, probably using threads. > > Over my dead body (the threads part that is). It has to be done with threads on Windows. But the threads don't escape from the select emulation. They are just tiny little threads which sit around waiting for something to happen on a file descriptor, and which post an event when it does. Ian