From: Ian Lance Taylor <ian@airs.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: RFA: Various Windows (mingw32) additions, mostly relating to select or serial ports
Date: Sat, 04 Feb 2006 17:06:00 -0000 [thread overview]
Message-ID: <m3vevvxde4.fsf@gossamer.airs.com> (raw)
In-Reply-To: <uhd7fo1qe.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> > Cc: gdb-patches@sourceware.org
> > From: Ian Lance Taylor <ian@airs.com>
> > Date: 03 Feb 2006 22:28:16 -0800
> >
> > The cleanest portable event loop which I know of is Tcl. The Tcl code
> > has solved pretty much all the event loop issues for Unix, Windows,
> > and MacOS 9.
>
> Can you, or someone else, please show a URL where I can see that event
> loop, without having to download the whole package?
Tcl is checked into the src repository, since it's part of expect
which is part of DejaGNU. There isn't just one place to look at the
event loop. The Windows pipe specific code is in
src/tcl/win/tclWinPipe.c.
Ian
next prev parent reply other threads:[~2006-02-04 17:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 22:05 Daniel Jacobowitz
2006-02-03 22:08 ` Daniel Jacobowitz
2006-02-04 12:43 ` Eli Zaretskii
2006-02-04 15:13 ` Daniel Jacobowitz
2006-02-04 6:28 ` Ian Lance Taylor
2006-02-04 10:30 ` Eli Zaretskii
2006-02-04 17:06 ` Ian Lance Taylor [this message]
2006-02-04 17:45 ` Eli Zaretskii
2006-02-04 15:00 ` Daniel Jacobowitz
2006-02-05 0:01 ` Ian Lance Taylor
2006-02-05 22:00 ` Daniel Jacobowitz
2006-02-06 3:27 ` Ian Lance Taylor
2006-02-06 4:03 ` Daniel Jacobowitz
2006-02-04 12:38 ` Eli Zaretskii
2006-02-04 15:11 ` Daniel Jacobowitz
2006-02-04 15:23 ` Eli Zaretskii
2006-02-04 15:30 ` Daniel Jacobowitz
2006-02-06 21:02 ` Daniel Jacobowitz
2006-02-06 23:02 ` Mark Kettenis
2006-02-06 23:17 ` Daniel Jacobowitz
2006-02-06 23:21 ` Christopher Faylor
2006-02-09 22:38 ` Daniel Jacobowitz
2006-02-10 7:53 ` Eli Zaretskii
2006-02-10 20:46 ` Mark Kettenis
2006-02-10 22:02 ` Daniel Jacobowitz
2006-02-07 4:41 ` Eli Zaretskii
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=m3vevvxde4.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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