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: Thoughts on a builtin read
Date: Tue, 21 Sep 1993 02:51:19 -0400	[thread overview]
Message-ID: <9309210651.AA18498@dahlie.techfak.uni-bielefeld.de> (raw)

[ Tom Culliton x2278 wrote: ]

    To keep things in the spirit of rc, simplicity should be our guiding
    principle.  This shapes most of the design decisions discussed below.

I always thought useability was the point ..

    1) One string rather than IFS seperation of fields
        - simplicity
        - preserves information, such as runs of blanks
        - field splitting can always be done later with backquote:
            read x;x=(`{echo -- $x})
...
    4) Should strip the newline
        - This makes "read x;echo -- $x" work right.

    5) Doesn't honor \ at EOL for continuation
        - simplicity

This is an inconsistency. I'd very much prefer the usual
        "x = `read"
    or  "x = `` ( $some_ifs_list ) { read }"

Malte


             reply	other threads:[~1993-09-21  6:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-09-21  6:51 malte [this message]
1993-09-21 14:19 ` Chris Siebenmann
  -- strict thread matches above, loose matches on Subject: below --
1993-09-22 17:18 Steve_Kilbane
1993-09-21 17:26 Arnold Robbins
1993-09-21 17:11 rsalz
1993-09-21 16:58 Arnold Robbins
1993-09-21 16:52 gjv%atlas%cesar
1993-09-21 16:36 Byron Rakitzis
1993-09-21 16:50 ` Chris Siebenmann
1993-09-21 15:56 malte
1993-09-21 17:02 ` Chris Siebenmann
1993-09-21 15:54 Tom Culliton x2278
1993-09-21 15:15 Alan Watson
1993-09-21 15:09 rsalz
1993-09-21 14:33 malte
1993-09-21 14:20 rsalz
1993-09-20 22:11 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=9309210651.AA18498@dahlie.techfak.uni-bielefeld.de \
    --to=malte@techfak.uni-bielefeld.de \
    --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).