9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Murdie <john@cs.york.ac.uk>
To: 9fans@cse.psu.edu
Cc: john@cs.york.ac.uk
Subject: Re: [9fans] v8 shell
Date: Fri, 14 Nov 2003 12:04:36 +0000	[thread overview]
Message-ID: <1068811476.1516.15.camel@pc118> (raw)
In-Reply-To: <a7892b11feb14cd18cac457811e32e2f@vitanuova.com>

On Fri, 2003-11-14 at 00:43, rog@vitanuova.com wrote:
> > like many people, I haven't been able to face the terminal moraine of rc, to get
> > to the mountain tops behind it. If only there was a budget for clue, and a
> > market for selling it in this area.
>
> erm, rc is dead easy...  much easier, in fact than the bourne shell
> (let alone all those unix abortions).
>
> the only (and crucial) thing that's really different is the fact that
> variables are (single level) lists.  this means you're no longer at
> the mercy of space-based tokenisation every time you use a $var
> expansion.  more-or-less everything else boils down to sugary
> syntactic differences.
>
> rc makes for a much more reliable scripting language.
>
> i can't really see why anyone would want to go back to the bourne
> shell when it's so fundamentally error-prone.

I agree with your conclusions, but I also like rc's use of \ for hiding
a new-line only, and rc's much simpler quoting rule - just one type of
quote ('), and double it for a literal quote. (The number of times I've
felt obliged to write a script with Bourne shell for portability to the
Linux world, only to get bogged down in quoted-quoted strings.) Ugh.

I always write rc shell scripts for my own use, these days - Plan 9 or
Unix. I find the minor differences between TD's original and Byron's
flattery are annoying, however. Will they ever be reconciled?

John A. Murdie
Department of Computer Science
University of York




  parent reply	other threads:[~2003-11-14 12:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.21.0311131606190.27715-100000@zenon.ceid.upatras.gr>
2003-11-13 16:06 ` Taj Khattra
2003-11-13 17:41   ` rob pike, esq.
2003-11-13 23:44     ` George Michaelson
2003-11-14  0:43       ` rog
2003-11-14  6:59         ` boyd, rounin
2003-11-17 10:26           ` Douglas A. Gwyn
2003-11-17 12:13             ` Charles Forsyth
2003-11-18  9:48               ` Douglas A. Gwyn
2003-11-14 12:04         ` John Murdie [this message]
2003-11-14 18:01           ` rog
2003-11-14 19:04             ` boyd, rounin
2003-11-14 19:18               ` rog
2003-11-14 19:31                 ` boyd, rounin
2003-11-14 22:25             ` Roman Shaposhnick
2003-11-16 11:45             ` Richard Miller
2003-11-16 12:01               ` Geoff Collyer
2003-11-16 12:21                 ` Richard Miller
2003-11-17 20:31                   ` rog
2003-11-16 14:23               ` Russ Cox
2003-11-16 14:35                 ` Richard Miller
2003-11-15 15:03           ` a
     [not found] ` <oprykztjlztsux9g@smtp.borf.com>
2003-11-14  0:41   ` boyd, rounin
2003-11-14 17:51     ` rog
2003-11-14 18:51       ` boyd, rounin
2003-11-17 10:26       ` Douglas A. Gwyn
2003-11-14  7:05   ` boyd, rounin
2003-11-14  8:13 boyd, rounin
2003-11-14 18:12 Richard C Bilson
2003-11-14 19:09 ` rog
2003-11-14 19:12 ` boyd, rounin

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=1068811476.1516.15.camel@pc118 \
    --to=john@cs.york.ac.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).