rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: malte@TechFak.Uni-Bielefeld.DE
To: rc@hawkwind.utcs.toronto.edu
Subject: Re:  list operators
Date: Thu, 16 Sep 1993 06:11:02 -0400	[thread overview]
Message-ID: <9309161011.AA08368@dahlie.techfak.uni-bielefeld.de> (raw)

Thanks to all of you for your quick answers! But let my summarize and
the take the discussion a little further:

    1) It is too late to introduce changes

It's not really a change since it doesn't change the semantics of existing,
valid scripts.

    2) The syntax is bad

Yes !! Maybe its an alt.tasteless candidate.

    3) A semantic improvement

I should have thought of that! Of course,
    ; x = ( 1 2 3 4 ) echo $x( -1 -3 )
    2 4
is much better.

    4) Why not use a function

Thanks to all who disclosed their solutions, but I already had some. I think,
there's more then one point of view to it:
Experienced rc users certainly don't have problems to write a function doing
the work, to put it in some kind of library and to reuse it on other occasions.
But the notion of "omit it if you can write a function" doesn't help novices
and - be honest to yourself - isn't it boring that you always have to source
some other file to include a function in your script ( . /some/file || exit )?
So it's speed and beauty vs usability. I'm still convinced my suggestions
enhance both.


             reply	other threads:[~1993-09-16 10:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-09-16 10:11 malte [this message]
  -- strict thread matches above, loose matches on Subject: below --
1993-09-17 17:32 Stefan Dalibor
1993-09-15 21:04 Tom Culliton x2278
1993-09-15 20:47 Brynjulv Hauksson
1993-09-15 19:38 Tom Culliton x2278
1993-09-15 20:08 ` Charles Hannum
1993-09-15 19:01 rsalz
1993-09-15 18:29 Byron Rakitzis
1993-09-15 18:28 malte
1993-09-15 18:07 rsalz
1993-09-15 17:55 malte

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=9309161011.AA08368@dahlie.techfak.uni-bielefeld.de \
    --to=malte@techfak.uni-bielefeld.de \
    --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).