From: "Boyd Roberts" <boyd@noos.fr>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] cooperative threads
Date: Sat, 19 Aug 2000 00:56:43 +0200 [thread overview]
Message-ID: <03db01c00967$945bcea0$03c684c3@psychobasketcase.org> (raw)
In-Reply-To: <200008182206.SAA19560@cse.psu.edu>
> As demonstrated by early versions of Windows
> and the Macintosh OS, reliance on cooperative
> threading alone is a recipe for disaster, since
> it requires that all threads be bug free. Thus,
> used as an OS's primary scheduling mechanism,
> cooperative threading requires that all executing
> programs be bug free, a very strong and very
> unlikely condition. In that arena, cooperative
> threading is not the right framework.
>
not only that. windows is event driven and i have
a zillion example where WinSock messages arrive
_out of order_.
ie. you can get write-true _before_ connect.
btw: i'm only admitting this through unfortunate
knowledge that i've gained from 2 years of
2 years of windows 3/95/NT coding -- and they
told me it was gonna be a 'unix tcp/ip'
contract. i needed a job, in paris, so i
said ok.
anyway, given the ghastly environment, it's _very_
hard to write a (bug free) windows program.
next prev parent reply other threads:[~2000-08-18 22:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-18 22:06 Russ Cox
2000-08-18 22:56 ` Boyd Roberts [this message]
2000-08-19 6:34 ` Lucio De Re
2000-08-21 8:59 ` Douglas A. Gwyn
2000-08-21 13:01 rob pike
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='03db01c00967$945bcea0$03c684c3@psychobasketcase.org' \
--to=boyd@noos.fr \
--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).