From: Chet Ramey <chet.ramey@case.edu>
To: Harald van Dijk <harald@gigawatt.nl>
Cc: Eric Blake <eblake@redhat.com>, dash <dash@vger.kernel.org>,
chet.ramey@case.edu
Subject: Re: [PATCH] Fix variable assignments in function invocations
Date: Fri, 09 Jan 2015 14:36:06 -0500 [thread overview]
Message-ID: <54B02DA6.1010003@case.edu> (raw)
In-Reply-To: <54B01242.9000907@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 1/9/15 12:39 PM, Eric Blake wrote:
> This behavior is tricky. Here's the latest POSIX wording:
> http://austingroupbugs.net/view.php?id=654#c1559
The currently-published standard (as far as I know, I7 TC1 has not been
published yet) requires the dash behavior. Bash implements it in
Posix mode. Both shells will remain conformant when TC1 comes out.
See
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_09_05
which includes
"When a function is executed, it shall have the syntax-error and variable-
assignment properties described for special built-in utilities in the
enumerated list at the beginning of Special Built-In Utilities."
- --
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
iEYEARECAAYFAlSwLaYACgkQu1hp8GTqdKsSTgCfaLS1d4s/Mtr56BRVmiO37rDj
MooAnRQZ50E86M/xLRsngYRe33fDCxFa
=jlKx
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2015-01-09 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 17:17 [PATCH] Fix variable assignments in function invocations Harald van Dijk
2015-01-09 17:39 ` Eric Blake
2015-01-09 17:55 ` Harald van Dijk
2015-01-09 19:36 ` Chet Ramey [this message]
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=54B02DA6.1010003@case.edu \
--to=chet.ramey@case.edu \
--cc=dash@vger.kernel.org \
--cc=eblake@redhat.com \
--cc=harald@gigawatt.nl \
/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).