From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] threads in Plan 9
Date: Fri, 27 Apr 2001 22:39:49 +0100 [thread overview]
Message-ID: <20010427214248.B923B19A02@mail.cse.psu.edu> (raw)
>>On a slightly different topic, it has also seemed hazardous to me in
>>Plan 9. One particular thing, for example, is that there's no way to
>>tell the system that a cohort of processes should be treated as such.
there are a few little traps and pitfalls in limbo/inferno too.
it's tricky, because there are conflicting requirements.
recently i've had to look at XML and its near and far relations.
it is fascinating how close they skirt to undecidability.
is that good or bad? i can't decide.
next reply other threads:[~2001-04-27 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-27 21:39 forsyth [this message]
2001-04-30 9:24 ` Douglas A. Gwyn
-- strict thread matches above, loose matches on Subject: below --
2001-04-28 16:00 Richard Miller
2001-04-27 20:06 jmk
2001-04-27 19:09 [9fans] Awk or Limbo ? geoff.9fans
2001-04-27 19:23 ` [9fans] threads in Plan 9 Scott Schwartz
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=20010427214248.B923B19A02@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--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).