From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9fans-ego-wars?
Date: Fri, 26 Sep 2003 20:43:49 +0100 [thread overview]
Message-ID: <5f54679ad3aaa0a6df1f03d4d103efd7@vitanuova.com> (raw)
In-Reply-To: <25494.135.214.150.100.1064606399.squirrel@www.infernopark.com>
>>I dont know how to put it but if I am right, Limbo is very good but one
>>cant use it for low level programming (like GC reducing predicatable
>>timing). C can be used well for low-level programming but there are
ESPOL was an extended subset of the Burroughs Extended ALGOL language
that was tuned to implement systems programs such as the operating system (MCP).
(i'd hoped the MCP source code was online by now but i couldn't find it;
its use of call-by-name to wait for an event was fascinating.)
anyhow, i thought it would be not too hard to do the same for Limbo,
once i'd decided it was really a sensible idea, that is.
i did think that in practice it might boil down to just preventing
the use of expensive things and limiting it to reference counting,
which could probably be done without actually creating a true dialect.
next prev parent reply other threads:[~2003-09-26 19:43 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 17:34 Sam
2003-09-25 18:31 ` Dan Cross
2003-09-25 19:25 ` boyd, rounin
2003-09-25 19:30 ` SPAM: " Charles Forsyth
2003-09-25 19:35 ` David Presotto
2003-09-25 19:57 ` Charles Forsyth
2003-09-25 20:28 ` boyd, rounin
2003-09-25 20:48 ` SPAM: " C H Forsyth
2003-09-25 22:07 ` ron minnich
2003-09-25 22:12 ` boyd, rounin
2003-09-25 22:14 ` Tristan Seligmann
2003-09-25 22:35 ` boyd, rounin
2003-09-25 23:28 ` Tristan Seligmann
2003-09-25 20:30 ` boyd, rounin
2003-09-25 20:40 ` SPAM: " C H Forsyth
2003-09-26 7:54 ` Fco.J.Ballesteros
2003-09-25 22:42 ` Andrew Simmons
2003-09-25 23:02 ` David Presotto
2003-09-25 23:07 ` ron minnich
2003-09-25 23:19 ` Charles Forsyth
2003-09-26 0:34 ` Charles Forsyth
2003-09-26 2:38 ` vdharani
2003-09-26 1:59 ` boyd, rounin
2003-09-26 9:40 ` Charles Forsyth
2003-09-26 19:59 ` vdharani
2003-09-26 19:43 ` C H Forsyth [this message]
2003-09-26 21:11 ` boyd, rounin
2003-09-27 16:19 ` a
2003-09-27 16:24 ` Brantley Coile
2003-09-27 16:36 ` a
2003-09-27 22:48 ` ron minnich
2003-09-29 2:37 ` okamoto
2003-09-29 2:38 ` boyd
2003-09-29 3:01 ` okamoto
2003-09-29 3:14 ` boyd
2003-09-29 3:20 ` okamoto
2003-09-29 3:22 ` boyd
2003-09-29 9:34 ` Vester Thacker
2003-09-29 9:40 ` boyd
2003-09-29 10:03 ` Vester Thacker
2003-09-29 10:11 ` boyd
2003-09-29 10:28 ` Vester Thacker
2003-09-29 11:18 ` David Presotto
2003-09-29 11:24 ` boyd
2003-09-29 9:13 ` bs
2003-09-26 21:06 ` boyd, rounin
2003-09-26 6:01 ` Skip Tavakkolian
2003-09-25 23:54 ` boyd, rounin
2003-09-25 23:08 ` Charles Forsyth
2003-09-25 23:11 ` Andrew Simmons
2003-09-25 23:57 ` boyd, rounin
2003-09-26 0:42 ` Andrew Simmons
2003-09-26 0:59 ` boyd, rounin
2003-09-26 1:05 ` D. Brownlee
2003-09-26 1:28 ` boyd, rounin
2003-09-25 20:13 ` Ishwar Rattan
2003-09-26 16:22 Dan Cross
2003-09-27 0:29 Dennis Ritchie
2003-09-29 9:13 ` Douglas A. Gwyn
2003-09-27 23:28 bs
2003-09-28 18:48 ` Charles Forsyth
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=5f54679ad3aaa0a6df1f03d4d103efd7@vitanuova.com \
--to=forsyth@vitanuova.com \
--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).