From: Eric Blake <eblake@redhat.com>
To: Heiko Gerstung <heiko@am-anger-1.de>
Cc: dash@vger.kernel.org
Subject: Re: Dashhh
Date: Thu, 17 Nov 2011 10:56:10 -0700 [thread overview]
Message-ID: <4EC54ABA.6050607@redhat.com> (raw)
In-Reply-To: <4EC53397.2030005@am-anger-1.de>
[-- Attachment #1: Type: text/plain, Size: 1617 bytes --]
On 11/17/2011 09:17 AM, Heiko Gerstung wrote:
> What this tiny patch does:
> - shift does not return a critical error when no arguments are left, it simply does nothing
This came up in the Austin Group (the folks in charge of POSIX), and the
consensus there was that dash is compliant (POSIX says that the problem
is with the script, not the shell, if you call shift with too few
positional parameters set; and that you should rewrite your script to
avoid tickling unspecified behavior).
http://austingroupbugs.net/view.php?id=459
> - "[[" works exactly as "["
Wrong. [[ is NOT exactly like [. And the Austin Group is currently
considering a proposal to add [[ to the shell (if that is done, then
dash will HAVE to implement it as specified by POSIX; but the jury's
still out on whether the proposal will be accepted):
http://austingroupbugs.net/view.php?id=375
> - "==" works like "="
That same Austin Group proposal is also talking about adding [ a == b ];
this particular addition is much less controversial than the [[
addition, so it is likely that the proposal will be split and each
separate addition individually balloted for inclusion.
> - the variable FUNCNAME contains the name of the currently running shell function or nothing (when not inside a function)
That's fluff - POSIX doesn't speak either way, and dash prefers to be as
light as possible when POSIX doesn't require it, so I'm not sure if
you'll get any enthusiastic response on this front.
--
Eric Blake eblake@redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
next prev parent reply other threads:[~2011-11-17 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 16:17 Dashhh Heiko Gerstung
2011-11-17 17:21 ` Dashhh Stefano Lattarini
2011-11-17 20:07 ` Dashhh Heiko Gerstung
2011-11-18 10:50 ` Dashhh Stefano Lattarini
2011-11-17 17:56 ` Eric Blake [this message]
2011-11-17 20:40 ` Dashhh Heiko Gerstung
2011-11-17 20:11 ` Dashhh Stephane CHAZELAS
2011-11-17 20:38 ` Dashhh Eric Blake
2011-11-18 8:18 ` Dashhh Stephane CHAZELAS
2011-11-17 20:46 ` Dashhh Heiko Gerstung
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=4EC54ABA.6050607@redhat.com \
--to=eblake@redhat.com \
--cc=dash@vger.kernel.org \
--cc=heiko@am-anger-1.de \
/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