Nathan Wiger wrote:
> Well, this is not bad, only it's not without its problems. Say you
> wanted to get your indices implicitly:
>
> @a[getindices()];
> @a[$r->get_x, $r->get_y];
@a["@{\(getindices())}"];
@a[join $",$r->get_x, $r->get_y];
> Either of these could return an arrayref, but forcing quotes around them
> means you'll need inbetweener variables or the @{} construct, neither of
> which is really gracious.
>
> I'm not trying to shoot the idea down point-blank, but I think it has
> some practical usage problems that potentially overshadow the gains in
> clarity.
>
> -Nate
I think I'm going to add it to my rewrite of my little RFC about
adding "sort order" to hashes and make that a big RFC about unified
containers, their access, transparent variations on their implementations
as trees or large contiguous blocks, and introduce the concept of numeric-keyed
containers that are not limited to integers, for all those freaks who collect
data points generated by strange attractors.
--
David Nicol 816.235.1187 [EMAIL PROTECTED]
Kansas City Perl Mongers will meet Sept. 20th at 7:00 in
Westport Flea Market Bar & Grill http://tipjar.com/kcpm
