rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: culliton@srg.af.mil (Tom Culliton x2278)
To: haahr@mv.us.adobe.com
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re:  Differences between Duff's rc and Byron's
Date: Wed, 26 May 1993 13:38:26 -0400	[thread overview]
Message-ID: <9305261338.aa04012@ceres.srg.af.mil> (raw)

Paul Hahr writes:

> > - $" vs. $^
> > > This seems like an arbitrary difference.
> Byron's $^ preceeded td's $".  if you look at older versions of the
> bell labs rc man page, it's not there.

I seemed to remember something like this and wondered why Duff did it
different.
 
> > - pattern matching, word vs. list
> > > This fixes something noted as a bug in the Plan 9 man page.
> i don't know what you mean by this comment.  i don't think Byron's
> ~ operator is any different from td's.

The Plan 9 man pages say "~ subject pattern ..." where subject is
singular (Duff's paper says "a string") and under BUGS the Plan 9 man
page says "There should be a way to match patterns against whole lists
rather than just single strings."  Byron allows subject to be a list.

I also forgot one we discussed before, functions that look like path
names, i.e. "fn /bin/csh { echo 'you''ve got to be kidding!' }" are
allowed in Duff's rc.  There are probably more minor differences like
this that got missed.

Tom


             reply	other threads:[~1993-05-26 17:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-05-26 17:38 Tom Culliton x2278 [this message]
  -- strict thread matches above, loose matches on Subject: below --
1993-05-27  6:48 Paul Haahr
1993-05-27  5:02 Alan Watson
1993-05-26 17:58 Paul Haahr
1993-05-26 20:31 ` Chris Siebenmann
1993-05-26 20:32 ` Chris Siebenmann
1993-05-26 17:06 Paul Haahr
1993-05-26 16:53 Paul Haahr
1993-05-26 17:55 ` Chris Siebenmann
1993-05-29 12:34   ` John Mackin
1993-05-25 23:32 Alan Watson
1993-05-25 22:42 Tom Culliton x2278

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=9305261338.aa04012@ceres.srg.af.mil \
    --to=culliton@srg.af.mil \
    --cc=haahr@mv.us.adobe.com \
    --cc=rc@hawkwind.utcs.toronto.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).