From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] vfork and paging
Date: Wed, 3 Oct 2001 12:52:13 +0200 [thread overview]
Message-ID: <061e01c14bf9$76276e00$a2b9c6d4@SOMA> (raw)
In-Reply-To: <20011003094521.3E7BF19A3C@mail.cse.psu.edu>
> writing correct programs is hard, but the addition of concurrency
> need not make it harder, ...
perhaps, but it really does depend on the underlying environment.
windoze is a prime example. that horrible, event driven, ghastly
mess makes it near impossible to write a program that even works.
take winsock -- the messages arrive in a random order; i've seen
'write true' turn up before 'connected'. yup, add another case
into the switch. and the idiots write stuff that exploit weird
junk like do an async connect and then wait/loop for 'write true'
in braindamaged ways.
next prev parent reply other threads:[~2001-10-03 10:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 9:49 forsyth
2001-10-03 10:52 ` Boyd Roberts [this message]
2001-10-03 13:55 ` Borja Marcos
2001-10-03 14:23 ` Ronald G Minnich
-- strict thread matches above, loose matches on Subject: below --
2001-10-19 21:03 David Gordon Hogan
2001-10-04 16:29 forsyth
2001-10-04 14:09 rog
2001-10-04 10:17 Richard Miller
2001-10-03 10:16 rog
2001-10-03 10:31 ` Boyd Roberts
2001-10-02 21:05 forsyth
2001-10-02 19:25 rob pike
2001-10-02 18:51 rog
2001-10-02 18:05 Russ Cox
2001-10-02 15:56 rob pike
2001-10-02 15:39 rog
2001-10-03 7:38 ` Boyd Roberts
2001-10-02 15:27 Fco.J.Ballesteros
2001-10-02 14:37 Sape Mullender
2001-10-02 14:31 rog
2001-10-02 14:29 presotto
2001-10-02 14:12 rog
2001-10-02 13:48 Sape Mullender
2001-10-02 13:47 rob pike
2001-10-02 13:42 Sape Mullender
2001-10-01 14:06 rob pike
2001-10-01 15:42 ` Douglas A. Gwyn
2001-10-01 14:01 forsyth
2001-10-01 12:21 rob pike
2001-10-02 8:27 ` Boyd Roberts
2001-10-02 13:34 ` Ronald G Minnich
2001-10-01 10:45 forsyth
2001-10-01 10:59 ` Boyd Roberts
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='061e01c14bf9$76276e00$a2b9c6d4@SOMA' \
--to=boyd@fr.inter.net \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).