DASH Shell discussions
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Paul Gilmartin <PaulGBoulder@aim.com>,
	Harald van Dijk <harald@gigawatt.nl>,
	dash@vger.kernel.org
Subject: Re: [PATCH] \e in "echo" and "printf" builtins
Date: Mon, 30 Jun 2014 07:08:34 -0600	[thread overview]
Message-ID: <53B16152.6040408@redhat.com> (raw)
In-Reply-To: <3DBAFEEE-9555-483E-8260-7D5E9B47F9AD@aim.com>

[-- Attachment #1: Type: text/plain, Size: 635 bytes --]

On 06/28/2014 11:33 AM, Paul Gilmartin wrote:
> 
> OTOH, there's a POSIX requirement that builtins be indistinguishable
> (except in performance) from the corresponding executables. 


The POSIX requirement only applies to portable uses of the builtin - ie.
those that are prescribed by POSIX.  Since POSIX does not require \e,
dash is not failing compliance, even if it differs from extensions
provided by corresponding executables.  I do not think dash needs to
bloat for \e unless POSIX standardizes it first.

-- 
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: 604 bytes --]

      parent reply	other threads:[~2014-06-30 13:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-28  4:56 [PATCH] \e in "echo" and "printf" builtins Adam Borowski
2014-06-28 16:52 ` Harald van Dijk
2014-06-28 17:27   ` Adam Borowski
2014-07-23  9:11     ` Adam Borowski
2014-07-23 10:26       ` Jérémie Courrèges-Anglas
2014-06-28 17:33   ` Paul Gilmartin
2014-06-29  9:28     ` Harald van Dijk
2014-06-30 13:08     ` Eric Blake [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=53B16152.6040408@redhat.com \
    --to=eblake@redhat.com \
    --cc=PaulGBoulder@aim.com \
    --cc=dash@vger.kernel.org \
    --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