From: Kamil Dudka <kdudka@redhat.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH 2/2] clear the heredoc list in case par_event() fails
Date: Fri, 30 Nov 2018 13:53:47 +0100 [thread overview]
Message-ID: <30884911.Z0NPFsIS6F@kdudka-nb> (raw)
In-Reply-To: <1543512844.6025.28.camel@samsung.com>
On Thursday, November 29, 2018 6:34:04 PM CET Peter Stephenson wrote:
> On Thu, 2018-11-29 at 17:24 +0100, Kamil Dudka wrote:
> > Since the above patch was applied, zsh exits successfully (despite it
> > reports >
> > parse error) on the attached example:
> >
> >
> > % zsh parse-error.sh; echo $?
> > parse-error.sh:4: parse error
> > 0
> >
> >...
> >
> > cat <<EOF
> > $(print <<XXX
> > EOF
>
> I don't think the problem is with the changed code, which is signalling the
> error as it should. I think it's up above.
>
> There's some slightly icky linkage between lex errors and the top level
> requiring tok to be LEXERR. The simple fix using the existing
> signalling looks like the following. I definitely don't think the tok =
> LEXERR has a moral right to percolate through in the way it must
> previously have been doing to avoid this, and the lexer does certainly
> have the right to update the token when signalling a parse error, so
> (famous last words) it's hard to see what could be wrong with this...
>
> pws
>
> diff --git a/Src/lex.c b/Src/lex.c
> index fa29da3..f43bcc7 100644
> --- a/Src/lex.c
> +++ b/Src/lex.c
> @@ -1613,6 +1613,7 @@ parsestr(char **s)
> zerr("parse error near `%c'", err);
> else
> zerr("parse error");
> + tok = LEXERR;
> }
> }
> return err;
Thanks for the quick fix! It seems to work perfectly.
Kamil
next prev parent reply other threads:[~2018-11-30 12:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 13:25 [PATCH 1/2] report bad ELF interpreter if it causes exec to fail Kamil Dudka
2015-04-17 13:25 ` [PATCH 2/2] clear the heredoc list in case par_event() fails Kamil Dudka
2015-04-17 19:17 ` Peter Stephenson
2015-04-20 8:48 ` Kamil Dudka
2018-11-29 16:24 ` Kamil Dudka
2018-11-29 17:34 ` Peter Stephenson
2018-11-29 18:39 ` Bart Schaefer
2018-11-30 9:55 ` Peter Stephenson
2018-11-30 12:53 ` Kamil Dudka [this message]
2015-04-17 13:49 ` [PATCH 1/2] report bad ELF interpreter if it causes exec to fail Daniel Shahaf
2015-04-17 14:32 ` Kamil Dudka
2015-04-17 15:21 ` Oliver Kiddle
2015-04-17 15:59 ` Kamil Dudka
2015-04-17 19:59 ` Oliver Kiddle
2015-04-17 15:41 ` Philippe Troin
2015-04-17 15:51 ` Bart Schaefer
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=30884911.Z0NPFsIS6F@kdudka-nb \
--to=kdudka@redhat.com \
--cc=p.stephenson@samsung.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).