rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Alan Watson <alan@oldp.astro.wisc.edu>
To: Richard Brooksby <richard@harlequin.co.uk>
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: A delicious thought
Date: Wed, 19 May 1993 10:04:31 -0400	[thread overview]
Message-ID: <9305191404.AA05715@oldp.astro.wisc.edu> (raw)

[Hi, Richard, remember me from GROGGS way back?]

Richard Brooksby 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.

Like I said, I didn't even suggest this.

> 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.

Not in rc; perhaps in es.  rc is the clean(er) and simple(r) one, remember.

The difference between rc and es is that rc makes the choices for you,
so you don't have the opportunity to get them wrong :-).


             reply	other threads:[~1993-05-19 14:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-05-19 14:04 Alan Watson [this message]
  -- strict thread matches above, loose matches on Subject: below --
1993-05-18 18:19 Alan Watson
1993-05-19 10:00 ` Richard Brooksby
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=9305191404.AA05715@oldp.astro.wisc.edu \
    --to=alan@oldp.astro.wisc.edu \
    --cc=rc@hawkwind.utcs.toronto.edu \
    --cc=richard@harlequin.co.uk \
    /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).