From: Todd Whitesel <toddpw@windriver.com>
To: ac131313@cygnus.com (Andrew Cagney)
Cc: toddpw@windriver.com (Todd Whitesel),
jingham@apple.com (Jim Ingham),
gdb@sourceware.cygnus.com,
insight@sourceware.cygnus.com ("Insight (GDB GUI)")
Subject: Re: non-blocking reads/writes and event loops
Date: Wed, 14 Jun 2000 18:49:00 -0000 [thread overview]
Message-ID: <200006150149.SAA00358@alabama.wrs.com> (raw)
In-Reply-To: <394832F2.39D46459@cygnus.com>
> > Agreed. If the API designers are dumb enough to trust threads absolutely,
> > and don't give us an option, then well, that's life.
>
> For what it is worth, here is the ``It is hard'' reason number two:
...
> Just making certain that your eyes are open :-)
No doubts about that. That's why I said "long term goal"...
--
Todd Whitesel
toddpw @ windriver.com
next prev parent reply other threads:[~2000-06-14 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-12 3:13 Andrew Cagney
2000-06-12 18:47 ` Todd Whitesel
2000-06-14 10:07 ` Jim Ingham
2000-06-14 10:47 ` Todd Whitesel
2000-06-14 18:37 ` Andrew Cagney
2000-06-14 18:49 ` Todd Whitesel [this message]
2000-06-18 22:21 ` Andrew Cagney
2000-06-18 22:46 ` Daniel Berlin
2000-06-20 10:20 ` Jim Blandy
2000-06-20 3:43 ` Todd Whitesel
2000-06-20 7:35 ` Elena Zannoni
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=200006150149.SAA00358@alabama.wrs.com \
--to=toddpw@windriver.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=jingham@apple.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).