From: malte@techfak.uni-bielefeld.de
To: rc@archone.tamu.edu
Subject: a word about shift
Date: Wed, 11 Sep 1991 17:10:34 -0000 [thread overview]
Message-ID: <9109111710.AA06478@dahlie.techfak.uni-bielefeld.de> (raw)
I'd like to raise a discussion about shift's behaviour.
There are two things I am not too content with:
1) shift doesn't work on any other variables than *
What about an extended shift, say shift var number,
or shift number, where the latter assumes * is to be shifted.
This preserves compatibility.
2) When $#var is lower than the number of shifts, shift prints an
error message and does nothing. I'd prefer shift would optionally
a) just print an error message,
b) print an error and set var to (),
c) be silent and set var to (),
d) do nothing
What about this? Anyone experienced out there?
_______________________________________________________________________________
malte@techfak.uni-bielefeld.de
send mail to: Universitaet Bielefeld, Technische Fakultaet
z. Hd. Malte Uhl
Postfach 8640
4800 Bielefeld 1
next reply other threads:[~1991-09-11 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-09-11 17:10 malte [this message]
1991-09-11 17:29 ` Chris Siebenmann
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=9109111710.AA06478@dahlie.techfak.uni-bielefeld.de \
--to=malte@techfak.uni-bielefeld.de \
--cc=rc@archone.tamu.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).