rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Markus Friedl <Markus.Friedl@informatik.uni-erlangen.de>
To: Decklin Foster <fosterd@hartwick.edu>
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: what if?, suggestion to re-instate the alternative if not syntax...
Date: Thu, 9 Dec 1999 03:22:31 -0500	[thread overview]
Message-ID: <19991209092231.B26932@faui01.informatik.uni-erlangen.de> (raw)
In-Reply-To: <19991209030021.C305@debian>; from fosterd@hartwick.edu on Thu, Dec 09, 1999 at 03:00:21AM -0500

On Thu, Dec 09, 1999 at 03:00:21AM -0500, Decklin Foster wrote:
> Bengt Kleberg writes:
> > Would it be possible to re-instate if not, ie the weird way of
> > writing } else { that was  around in rc in the very beginning? (and
> > still is in Plan9 rc).
> I'm curious, what is this syntax?

the 'if not' syntax.
please read http://www.star.le.ac.uk/~tjg/rc/misc/td.html

	if(test -f /tmp/$i) echo $i already in /tmp
	if not cp $i /tmp

> Anyway, my real question is, how
> important is being exactly like the original rc as a design
> consideration of this shell? I was recently thinking that i would have
> used 'foreach foo (bar)' (like Perl) instead of 'for (foo in bar)'.

why? this is a shell with a C-like syntax not a perl like
syntax. if you want perl go and use perl.

> But you couldn't go and change it now what with all these scripts
> already in place. Then there's my other message about mucking with ~.
> I can probably find more to complain about :-)

nope, rc is perfect.

  reply	other threads:[~1999-12-09  9:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-08 15:13 Bengt Kleberg
1999-12-09  8:00 ` Decklin Foster
1999-12-09  8:22   ` Markus Friedl [this message]
1999-12-09  8:13 Byron Rakitzis
1999-12-10  9:00 Bengt Kleberg
1999-12-10  9:06 Bengt Kleberg

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19991209092231.B26932@faui01.informatik.uni-erlangen.de \
    --to=markus.friedl@informatik.uni-erlangen.de \
    --cc=fosterd@hartwick.edu \
    --cc=rc@hawkwind.utcs.toronto.edu \


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