From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: new and updated completions
Date: Thu, 9 Aug 2001 15:58:25 +0000 [thread overview]
Message-ID: <1010809155825.ZM1792@candle.brasslantern.com> (raw)
In-Reply-To: <3B71740F.3D92A203@yahoo.co.uk>
On Aug 8, 6:17pm, Oliver Kiddle wrote:
} Subject: Re: PATCH: new and updated completions
}
} Bart Schaefer wrote:
}
} > There is no reason, ever, to use $args[@].
} >
} > Either ksharrays is set, in which case you need ${args[@]}, or it is not
} > set, in which case $args is equivalent and microscopically faster.
}
} I had assumed that it was done this way for a reason such as handling
} a strange option combination or that it was considered more readable
} to have the [@] there. Maybe someone does have a reason?
In the argument list of a command, it might be done just to alert the
reader that multiple arguments are potentially being provided.
In an expression like `args=( $args[@] ... )', the extra info is minimal.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-08-09 15:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-06 14:28 Oliver Kiddle
2001-08-06 14:30 ` Chmouel Boudjnah
2001-08-06 17:43 ` Borsenkow Andrej
2001-08-06 17:47 ` Chmouel Boudjnah
2001-08-08 11:37 ` Oliver Kiddle
2001-08-08 12:06 ` Chmouel Boudjnah
2001-08-08 15:52 ` Bart Schaefer
2001-08-08 17:17 ` Oliver Kiddle
2001-08-09 15:58 ` Bart Schaefer [this message]
2001-08-11 14:20 ` Peter Stephenson
2001-08-07 10:36 ` Sven Wischnowsky
2001-08-07 11:04 ` Oliver Kiddle
2001-08-08 7:19 ` Sven Wischnowsky
2001-08-08 17:23 ` Oliver Kiddle
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=1010809155825.ZM1792@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).