From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Martijn Dekker <martijn@inlv.org>,
"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: [doc] "sh_word_split nothing to do with word splitting"?
Date: Fri, 16 Mar 2018 19:33:28 +0000 [thread overview]
Message-ID: <20180316193328.GC23397@chaz.gmail.com> (raw)
In-Reply-To: <CAH+w=7YHeTQCwfpHGXN=CBHX_4OcGKeMUFytNypaa5CxLDLA5g@mail.gmail.com>
2018-03-16 11:28:23 -0700, Bart Schaefer:
> On Fri, Mar 16, 2018 at 10:26 AM, Stephane Chazelas
> <stephane.chazelas@gmail.com> wrote:
> > So, how about this new take at it? Renders (in info) as:
> >
> > SH_WORD_SPLIT (-y) <K> <S>
> > Causes $IFS field splitting to be performed on unquoted parameter
> > expansions in addition to command substitutions. Note that
>
> This is OK, I just keep thinking there should be a reference back to
> the shell grammar; field splitting applies to anything identified in
> the grammar by the token WORD provided that the WORD is not quoted.
> Arithmetic expressions are treated as if double-quoted. That's really
> all there is to it.
Note that for $((text)), there's possible confusion. In the
POSIX spec, the reference to "as if double quoted" is about the
interpretation of text, not $((text)).
In POSIX, in $(($1 + 2)), $1 is not subject to split + glob
because $1 + 2 is treated as if quoted, but $(($1 + 2)) is
*required* (!) to be split+globbed.
As in:
IFS=2; echo $((11 * 11))
is *required* to output
1 1
but zsh, even in sh emulation outputs "121" as everyone would
expect.
That's why I mention it in the text to clarify that it's an
intentionaly deviation from the POSIX standard.
(I will try and have POSIX lift that silly requirement but I
have little hope they'll accept; note that a few shells have
already gone out of their way to change their sensible
behaviour to meet POSIX compliance on that front)
--
Stephane
next prev parent reply other threads:[~2018-03-16 19:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 9:44 Stephane Chazelas
2018-03-11 18:24 ` Bart Schaefer
2018-03-11 20:53 ` Stephane Chazelas
2018-03-11 23:41 ` Martijn Dekker
2018-03-12 7:43 ` Stephane Chazelas
2018-03-12 8:07 ` Stephane Chazelas
2018-03-16 17:26 ` Stephane Chazelas
2018-03-16 18:28 ` Bart Schaefer
2018-03-16 19:33 ` Stephane Chazelas [this message]
2018-03-24 20:17 ` Martijn Dekker
2018-03-25 6:42 ` Stephane Chazelas
2018-03-26 18:11 ` Martijn Dekker
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=20180316193328.GC23397@chaz.gmail.com \
--to=stephane.chazelas@gmail.com \
--cc=martijn@inlv.org \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).