From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from oldp.astro.wisc.edu ([128.104.39.15]) by hawkwind.utcs.toronto.edu with SMTP id <2689>; Wed, 19 May 1993 10:05:22 -0400 Received: by oldp.astro.wisc.edu (5.65/DEC-Ultrix/4.3) id AA05715; Wed, 19 May 1993 09:04:32 -0500 Message-Id: <9305191404.AA05715@oldp.astro.wisc.edu> To: Richard Brooksby Cc: rc@hawkwind.utcs.toronto.edu Subject: Re: A delicious thought Date: Wed, 19 May 1993 10:04:31 -0400 From: Alan Watson X-Mts: smtp [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 :-).