On Fri, 1 Sep 2000 13:25:07 +1100 (EST), Damian Conway wrote: >More than anything I think the inability to write C<sub list> DWIMishly >argues that we need it built-in. But we also need a *very* careful design >of the semantics. Well, except that it isn't clear which DWIM you want. Does DWIM mean, the effect that you don't have if you drop that proposed keyword? It's the most powerful construct, but also very intransparent. I don't like that. Let's fall back to what we have already: $\ = "\n"; print $a = () = qw(a b c); --> 3 All those who expected that the list would be evaluated in array (not list!) context, raise your hands. Not many, I would think. -- Bart.
- Re: Change "($one, $two)=" b... Nathan Wiger
- Re: Change "($one, $two)=" b... Tom Hughes
- Re: Change "($one, $two)=" b... Jeremy Howard
- Re: Change "($one, $two)=" b... Damian Conway
- Re: Change "($one, $two)=" b... Tom Christiansen
- Re: Change "($one, $two)=" b... Nathan Wiger
- Re: Change "($one, $two)=" b... Peter Scott
- Re: Change "($one, $two)=" b... Jeremy Howard
- Re: Change "($one, $two)=" b... Nathan Wiger
- Re: RFC 175 (v1) Add C<list> keyword to forc... Randal L. Schwartz
- Re: RFC 175 (v1) Add C<list> keyword to force lis... Bart Lateur
- Re: RFC 175 (v1) Add C<list> keyword to forc... Tom Christiansen
- Re: RFC 175 (v1) Add C<list> keyword to forc... Tom Christiansen
- Re: RFC 175 (v1) Add C<list> keyword to ... Bart Lateur
- Re: RFC 175 (v1) Add C<list> keyword... Tom Christiansen
- Re: RFC 175 (v1) Add C<list> keyword... Tom Christiansen
- Re: RFC 175 (v1) Add C<list> keyword to forc... John Porter