From: Jilles Tjoelker <email@example.com>
To: Harald van Dijk <firstname.lastname@example.org>
Cc: Eric Blake <email@example.com>, firstname.lastname@example.org
Subject: Re: declaration utilities (was: [bug-diffutils] bug#24116: [platform-testers] new snapshot available: diffutils-3.3.50-0353)
Date: Wed, 24 Aug 2016 00:04:47 +0200 [thread overview]
Message-ID: <20160823220447.GB57473@stack.nl> (raw)
On Fri, Aug 05, 2016 at 07:15:02PM +0200, Harald van Dijk wrote:
> On 05/08/2016 18:21, Eric Blake wrote:
> > On 08/05/2016 07:13 AM, Harald van Dijk wrote:
> >> Unfortunately, POSIX currently requires the export command to not have
> >> any magic quoting, and any POSIX-conforming shell will make
> >> a="b c=d"
> >> export a=$a
> >> set a to b, and c to d. Not so with bash, but that's because bash simply
> >> isn't POSIX-conforming, even if invoked as sh.
> > Not quite so fast.
> >> POSIX will require special quoting rules for the export command in the
> >> future, similar to what bash does today. When it does, dash is likely to
> >> change to match that, and the local command will likely be changed to
> >> work the same way.
> > POSIX has already issued an interpretation request, and therefore, any
> > CURRENT implementations (including bash) that already behave as
> > permitted by the interpretation ARE conforming. [...]
> > http://austingroupbugs.net/view.php?id=351
> An interpretation request doesn't automatically mean that all current
> implementations are conforming, does it? It only means that when the
> interpretation response says so. In this case, the response says that
> the standard does not allow bash/ksh's behaviour.
> > Interpretation response
> > ------------------------
> > The standard states that the current behavior of ksh93 does not
> > conform, and conforming implementations must conform to this.
> > However, concerns have been raised about this which are being
> > referred to the sponsor.
> The fact that this is seen as a defect in the standard which will be
> fixed, rather than a defect in bash/ksh, doesn't make bash/ksh conform,
> it merely means that bash/ksh shouldn't be changed to conform.
Although it is certainly true that the current standard forbids special
quoting rules for export and readonly, making this change sooner rather
than later will be helpful to users.
Looking at ChangeLog.O, I can see dash had special quoting rules for
export, readonly and local between 1997 and 2001. They were removed,
basically, because there was no specification guidance. The
specification guidance is now available in the form of Austin group bug
Users of FreeBSD sh have likewise liked having these new rules
prev parent reply other threads:[~2016-08-23 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+8g5KEOBs=AtZoBZw7CJ5wW8=Yw88KrvjJK1PeEqK3uj_1wEg@mail.gmail.com>
[not found] ` <9C56E56C-4D31-46AB-AC75-1AA8A759BF4D@gmail.com>
[not found] ` <CA+8g5KGack9X8ByfoJEtbQHj-44iG6bvQ0yhguVqQ4vqZh4geA@mail.gmail.com>
2016-08-05 12:46 ` [bug-diffutils] bug#24116: [platform-testers] new snapshot available: diffutils-3.3.50-0353 Dave Gordon
2016-08-05 13:13 ` Harald van Dijk
2016-08-05 14:09 ` Dave Gordon
2016-08-05 16:21 ` Eric Blake
2016-08-05 17:15 ` Harald van Dijk
2016-08-23 22:04 ` Jilles Tjoelker [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).