From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: dash-0.5.9.1-1
Date: Mon, 27 Feb 2017 12:48:00 -0000 [thread overview]
Message-ID: <58b42005.a40a9d0a.b4b11.d2c5@mx.google.com> (raw)
In-Reply-To: <CAEhDDbAFXoh6_vCx5nnSyUhMd+t2CUnSBWLycEYetHVCufXvqQ@mail.gmail.com>
On Mon, 27 Feb 2017 11:20:54, Csaba Raduly wrote:
> Nice strawman argument.
> You seem to assume that Dash implements nothing beyond POSIX (and
> hence anything that runs on dash must run on every other shell). This
> is not the case.
Perhaps you should have read my full post. Here, let me quote myself and link
for you:
On Sat, 25 Feb 2017 09:08:55, Steven Penny wrote:
> #!/bin/bash -> script that follows might have Bashisms
> #!/bin/dash -> script that follows might have Dashisms (echo -n, local)
> #!/bin/sh -> script that follows should be a POSIX script
http://cygwin.com/ml/cygwin/2017-02/msg00320.html
So, as I said before and now again, Dash is a minimal shell, similar to POSIX
shell. Yes, it is possible to be in a situation like this:
- script has #!/bin/sh
- script has Dashisms, which can cause problem on POSIX shell
However being that "echo -n" and "local" are probably the only Dashisms, that is
trivial to fix. Compare to a Bash problem:
- script has #!/bin/sh
- script has Bashisms, which can cause problem on POSIX shell
Even switching from a Bash script to Dash script can be a herculean task, if the
script heavily relies on Bashisms like arrays, herestrings, process
substitution, etc.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-02-27 12:48 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 14:01 Eric Blake (cygwin)
2017-02-23 4:20 ` Steven Penny
2017-02-23 17:50 ` Andrey Repin
2017-02-23 19:46 ` Steven Penny
2017-02-23 19:59 ` Brian Inglis
2017-02-23 20:41 ` Eric Blake
2017-02-24 7:19 ` Yaakov Selkowitz
2017-02-23 23:44 ` Steven Penny
2017-02-24 14:32 ` Eric Blake
2017-02-24 19:19 ` Brian Inglis
2017-02-23 22:05 ` Andrey Repin
2017-02-23 23:01 ` Tony Kelman
2017-02-23 23:04 ` Eliot Moss
2017-02-23 23:12 ` Kenneth Wolcott
2017-02-23 23:30 ` Vince Rice
2017-02-23 23:35 ` Andrey Repin
2017-02-24 3:16 ` Larry Hall (Cygwin)
2017-02-24 3:18 ` Larry Hall (Cygwin)
2017-02-24 4:57 ` Steven Penny
2017-02-24 14:43 ` Eric Blake
2017-02-24 15:05 ` Lee Dilkie
2017-02-25 16:55 ` Steven Penny
2017-03-01 23:57 ` Matt Seitz (matseitz)
2017-02-23 23:33 ` Steven Penny
2017-02-25 16:46 ` cyg Simple
2017-02-25 17:09 ` Steven Penny
2017-02-27 10:20 ` Csaba Raduly
2017-02-27 12:48 ` Steven Penny [this message]
2017-02-27 23:13 ` Duncan Roe
2017-02-28 0:51 ` Steven Penny
2017-02-28 20:52 ` cyg Simple
2017-02-28 21:43 ` Steven Penny
2017-03-01 14:42 ` cyg Simple
2017-03-02 0:22 ` Steven Penny
2017-03-02 3:46 ` Vince Rice
2017-03-02 5:27 ` Steven Penny
2017-03-02 5:31 ` Vince Rice
2017-03-02 12:36 ` Steven Penny
2017-03-02 13:37 ` Marco Atzeri
2017-03-02 14:29 ` Eric Blake
2017-03-02 16:16 ` Nellis, Kenneth (Conduent)
2017-03-02 17:28 ` Brian Inglis
2017-03-02 18:45 ` Eric Blake
2017-03-02 23:23 ` Brian Inglis
2017-03-02 18:28 ` Achim Gratz
2017-03-02 14:31 ` Brian Inglis
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=58b42005.a40a9d0a.b4b11.d2c5@mx.google.com \
--to=svnpenn@gmail.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).