From: Richard Brooksby <richard@harlequin.co.uk>
To: alan@oldp.astro.wisc.edu
Cc: rc@hawkwind.utcs.toronto.edu, es@hawkwind.utcs.toronto.edu
Subject: Re: A delicious thought
Date: Wed, 19 May 1993 06:00:21 -0400 [thread overview]
Message-ID: <21463.9305191000@morris.harlqn.co.uk> (raw)
In-Reply-To: Alan Watson's message of Tue, 18 May 1993 14:19:12 -0400 <9305181819.AA22839@oldp.astro.wisc.edu>
Alan Watson <alan@oldp.astro.wisc.edu> wrote:
> You can't do cd et al. properly in the way I suggested, as rc does
> not keep all of its state in the environment...
:
> Of course, we could have rc realize its entire state in the
> environment, but I hear the wolves baying over in the es list, so I
> won't even suggest this.
What you are suggesting is just that rc should be continuation rather
than stack based. I doubt that even the es designers contemplated
this option, although it would make a very interesting shell.
However, since the Unix process model is stack based (process
parent/child relationships are just like a stack) it wouldn't mesh
very well.
A nicer thing, in my humble opinion, would be to include a foreign
function interface and allow dynamic linking to libraries. One could
then import Clib and make system calls directly.
---
Richard Brooksby <richard@harlequin.co.uk>
ML Project / Symbolic Processing Division / Harlequin
+44 223 872522
next prev parent reply other threads:[~1993-05-19 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-05-18 18:19 Alan Watson
1993-05-19 10:00 ` Richard Brooksby [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-05-19 14:04 Alan Watson
1993-05-18 17:10 Byron Rakitzis
1993-05-18 17:08 Arnold Robbins
1993-05-18 17:01 Alan Watson
1993-05-18 19:39 ` root
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=21463.9305191000@morris.harlqn.co.uk \
--to=richard@harlequin.co.uk \
--cc=alan@oldp.astro.wisc.edu \
--cc=es@hawkwind.utcs.toronto.edu \
--cc=rc@hawkwind.utcs.toronto.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).