From: Joerg Schilling <Joerg.Schilling@fokus.fraunhofer.de>
To: shwaresyst@aol.com, oleg@bulatov.me, eblake@redhat.com,
dash@vger.kernel.org, austin-group-l@opengroup.org
Subject: Re: heredoc and subshell
Date: Wed, 24 Feb 2016 13:32:23 +0100 [thread overview]
Message-ID: <56cda2d7.BQQZnsNWLLDg81ia%Joerg.Schilling@fokus.fraunhofer.de> (raw)
In-Reply-To: <153133f6f0b-66ff-2f8@webprd-a36.mail.aol.com>
Shware Systems <shwaresyst@aol.com> wrote:
> Near as I can tell, from 2.3, io_here has precedence over string concatenation of normal tokenization so the output of bash should be:
> A:echo line 1
> Syntax error: Missing right paren
> Syntax error: Missing closing double quote
>
> as the list production terminates at the first newline, and a new one doesn't start until after the second line with XXX to satisfy the second io_here. It can be argued provisions for trying to find the end of an open string should continue after the io_here body, but Item 7 of 2.3 has the newline terminating it.
So you are arguing that $(...) and `...` behave different?
The interesting news is that the Schily Bourne Shell and mksh currently behave
similar to what you like to see.
Jörg
--
EMail:joerg@schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'
next prev parent reply other threads:[~2016-02-24 12:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 22:07 heredoc and subshell Oleg Bulatov
2016-02-23 22:49 ` Eric Blake
2016-02-23 23:16 ` Eric Blake
[not found] ` <56CCE1E3.1060805-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-02-24 10:58 ` Joerg Schilling
[not found] ` <56cd8cd1.LdVYbpfe+0tQMm8I%Joerg.Schilling-8LS2qeF34IpklNlQbfROjRvVK+yQ3ZXh@public.gmane.org>
2016-02-24 12:27 ` Shware Systems
2016-02-24 12:32 ` Joerg Schilling [this message]
2016-02-24 20:27 ` Oleg Bulatov
2016-02-23 23:18 ` Jilles Tjoelker
2016-02-24 8:46 ` Thorsten Glaser
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=56cda2d7.BQQZnsNWLLDg81ia%Joerg.Schilling@fokus.fraunhofer.de \
--to=joerg.schilling@fokus.fraunhofer.de \
--cc=austin-group-l@opengroup.org \
--cc=dash@vger.kernel.org \
--cc=eblake@redhat.com \
--cc=oleg@bulatov.me \
--cc=shwaresyst@aol.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 NNTP newsgroup(s).