Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [PATCH] Make the parameter expansion subscript flags parse error message, "error in flags", identify the location of the parse error.
- X-seq: zsh-workers 48392
- From: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: [PATCH] Make the parameter expansion subscript flags parse error message, "error in flags", identify the location of the parse error.
- Date: Sun, 04 Apr 2021 17:27:05 +0100
- Archived-at: <https://zsh.org/zsh-workers/48392>
- Archived-at: <http://www.zsh.org/sympa/arcsearch_id/zsh-workers/2021-04/7a5b055845089cfd55bb0a37fce66a5cbc47c9d5.camel%40ntlworld.com>
- In-reply-to: <20210403024954.4321-1-danielsh@tarpaulin.shahaf.local2>
- List-id: <zsh-workers.zsh.org>
- References: <20210403024954.4321-1-danielsh@tarpaulin.shahaf.local2>
On Sat, 2021-04-03 at 02:49 +0000, Daniel Shahaf wrote:
> ---
> Review of the logic obtaining and massaging str_copy_for_output would be
> appreciated. It's a 2500-line function and there are multiple char*
> variables that refer to the same memory locations as *str, so it's
> conceivable I overlooked something.
I think this is early enough in the function it should be fine. It's
moving from left to right except where it needs to find something
matching, and the flags are first.
pws
Messages sorted by:
Reverse Date,
Date,
Thread,
Author