From: Harald van Dijk <email@example.com>
To: Eric Blake <firstname.lastname@example.org>,
Dave Gordon <email@example.com>,
Jim Meyering <firstname.lastname@example.org>,
Assaf Gordon <email@example.com>
Cc: firstname.lastname@example.org, email@example.com
Subject: Re: [bug-diffutils] bug#24116: [platform-testers] new snapshot available: diffutils-3.3.50-0353
Date: Fri, 5 Aug 2016 19:15:02 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
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. [...]
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.
next prev parent reply other threads:[~2016-08-05 17:15 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 [this message]
2016-08-23 22:04 ` declaration utilities (was: [bug-diffutils] bug#24116: [platform-testers] new snapshot available: diffutils-3.3.50-0353) Jilles Tjoelker
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).