From: haahr@kaleida.com (Paul Haahr)
To: rc@hawkwind.utcs.toronto.edu
Subject: shift
Date: Wed, 22 Sep 1993 13:21:12 -0400 [thread overview]
Message-ID: <9309221721.AA17501@talisman.kaleida.com> (raw)
biased as i might be, i'd like to point out the existence of es's
solution to the shift question:
+ no shift builtin
+ ... accepted in subscript arguments, where
$x(m ... n) means all elements of x between the mth
mth and nth (inclusive). if m is omitted, 1 is assumed.
if n is a omitted, $#x is assumed.
anyway, that's it. while
* = $*(2 ...)
is not as clean as
shift
the flexibility is, imho, worth it.
next reply other threads:[~1993-09-22 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-09-22 17:21 Paul Haahr [this message]
1993-09-22 18:05 shift 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=9309221721.AA17501@talisman.kaleida.com \
--to=haahr@kaleida.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).