From: "Gorka Guardiola" <paurea@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] How to move to rc from sh/bash
Date: Sun, 10 Feb 2008 17:59:02 +0100 [thread overview]
Message-ID: <599f06db0802100859l2a13a8e7o9d6a492138d44421@mail.gmail.com> (raw)
In-Reply-To: <b954b2060802082353h694ee9a3kd008351835d9f27a@mail.gmail.com>
On Feb 9, 2008 8:53 AM, Hongzheng Wang <wanghz@gmail.com> wrote:
> Hi all,
>
> 2. In non-interactive use (script programming), what's the main
> advantages of rc over sh/bash?
Things I like of rc:
In both interactive and non-interactive, spaces do not bite you in rc.
in bash
if [ $bla -eq $otherbla ] ; fi endif... ahhh, I can´t remember the
syntax and get the spaces wrong,
never know if I need endif or fi or...
if ( command ) {
}
I don´t need to remember spaces, or contrived grammar.
Also the operator ^ and the fact that it is distributive is really powerful.
Someone else said it, only one quoting simbol
(what does " bla \$e'o" do on bash?, I just invented it, but every time I see
double qoutes I start trembling)
The most important thing is that it is *simple*, it doesn´t have any feature
someone may have thought a shell may need because they didn´t know how
to use sed. It only has a well thought subset of complete features.
--
- curiosity sKilled the cat
next prev parent reply other threads:[~2008-02-10 16:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 7:53 Hongzheng Wang
2008-02-09 8:01 ` mattmobile
2008-02-09 8:41 ` Hongzheng Wang
2008-02-09 8:57 ` mattmobile
2008-02-09 9:00 ` erik quanstrom
2008-02-09 9:21 ` Hongzheng Wang
2008-02-09 10:11 ` Charles Forsyth
2008-02-09 10:27 ` Lluís Batlle
2008-02-09 15:06 ` Uriel
2008-02-09 17:54 ` Charles Forsyth
2008-02-09 21:59 ` geoff
2008-02-09 13:00 ` Anthony Sorace
2008-02-10 16:59 ` Gorka Guardiola [this message]
2008-02-10 17:16 ` Pietro Gagliardi
2008-02-10 17:47 ` erik quanstrom
2008-02-10 18:12 ` Martin Neubauer
2008-02-11 15:04 ` erik quanstrom
2008-02-11 23:03 ` Martin Neubauer
2008-02-11 23:25 ` Pietro Gagliardi
2008-02-20 15:04 ` maht
2008-02-20 15:08 ` Federico G. Benavento
2008-02-20 15:24 ` erik quanstrom
2008-02-20 15:55 ` maht
2008-02-11 23:59 ` Uriel
2008-02-12 11:57 ` Martin Neubauer
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=599f06db0802100859l2a13a8e7o9d6a492138d44421@mail.gmail.com \
--to=paurea@gmail.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).