Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [frederik@xxxxxxxxxxxxxxxx: Bug#236748: zsh: associative array documentation reference broken]
- X-seq: zsh-workers 19570
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: [frederik@xxxxxxxxxxxxxxxx: Bug#236748: zsh: associative array documentation reference broken]
- Date: Mon, 8 Mar 2004 22:19:59 +0000
- Cc: 236748-forwarded@xxxxxxxxxxxxxxx
- In-reply-to: <20040308152325.GB9385@xxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20040308152325.GB9385@xxxxxxxxxxx>
On Mar 8, 10:23am, Clint Adams wrote:
}
} For associative arrays, `[*]' or `[@]' evaluate to all the values
} (not the keys, but see Subscript Flags below), in no particular
} order.
}
} There is nothing relevant to this syntax under Subscript Flags.
Yes, there is. The k, K, and e subscript flags all affect the
intepretation of * and @. It's true that [(K)*] is nearly the same
as [*], but [(k)*] is quite different, as both [(k)@] and [(K)@] are
from [@].
} For associative arrays, `[*]' or `[@]' evaluate to all the values
} (not the keys, but see the documentation for the 'k' flag under
} Parameter Expansion Flags in zshexpn(1)), in no particular order.
No, this is NOT what it should say, or at least not ALL that it should
say.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author