Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: small parameter fix
- X-seq: zsh-workers 5685
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>
- Subject: Re: PATCH: small parameter fix
- Date: Mon, 8 Mar 1999 01:01:01 -0800 (PST)
- Cc: zsh-workers@xxxxxxxxxxxxxx
- In-reply-to: <199903080850.JAA11456@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <199903080850.JAA11456@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Reply-to: Bart Schaefer <schaefer@xxxxxxxxxxx>
Sven Wischnowsky writes:
>
> ...although I'm not sure if it was not intentional. If it was, I'd
> like to hear the reason. This:
>
> ${${...}[...]}
>
> previously didn't really work: if the inner ${...} produced an array
> with only one element, the outer ${...} treated it as a string and the
> subscript gave the n'th character.
AHA! This must be the reason that "${${(@)...}...}" is required in so
many mystifying circumstances. I, too, would like to hear whether the
previous behavior was intentional ... this change does potentially
break scripts, including I think 3.0.5 scripts, so we'd better tread
carefully.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author