From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Is there some bash source that Zsh will not parse?
Date: Thu, 11 Jul 2019 02:46:56 +0200 [thread overview]
Message-ID: <CAKc7PVD6QofiD1fvOb5qNXfos_Egr-kUdDEWq8gLdSB79n4Cpw@mail.gmail.com> (raw)
In-Reply-To: <20190710224713.GA30662@spodhuis.org>
On Thu, 11 Jul 2019 at 00:47, Phil Pennock
<zsh-workers+phil.pennock@spodhuis.org> wrote:
>
> On 2019-07-10 at 18:10 +0200, Sebastian Gniazdowski wrote:
> > in the opposite direction, this is rather true, e.g. the globbing
> > flags aren't parsed correctly:
>
> ...
> Note in particular that where zsh has ${(flags)varname} for parameter
> expansion flags, bash has ${varname@operator} syntax for expansion
> transformations. There's other stuff around indirect variables, case
> modification expansions, and `shopt`, which all come to mind. Almost
> certainly a lot more.
Yes but i meant actually just the parser. I believe the contents of
${...} are taken as a whole by the parser to then be passed to
stringsubst() and the like, so that would be a "late"-parsing, which
i'm not interested in currently.
> If Zsh's goals are changing such that complete Bash compatibility is
> required in bash mode (as opposed to "enough to get by") then it might
> be worth trying to run the bash test suite against Zsh, with suitable
> modifications to ensure Zsh is in the correct mode always.
> That should prove ... educational.
Yeah, that would be interesting :)
> -Phil
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org
prev parent reply other threads:[~2019-07-11 1:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 16:10 Sebastian Gniazdowski
2019-07-10 22:47 ` Phil Pennock
2019-07-11 0:46 ` Sebastian Gniazdowski [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=CAKc7PVD6QofiD1fvOb5qNXfos_Egr-kUdDEWq8gLdSB79n4Cpw@mail.gmail.com \
--to=sgniazdowski@gmail.com \
--cc=zsh-users@zsh.org \
--cc=zsh-workers+phil.pennock@spodhuis.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).