Re: Change "($one, $two)=" behavior for optimization? (was Re: RFC 175 (v1) Add C keyword toforcelist context (like C))

2000-09-04 Thread Nathan Wiger
I know I just promised to be quiet... but I realized something really important. If the first arg returned from want() isn't the context, then this: > In Perl 6 we switch with Ces, mister! ("Muro volente", of course ;-) > > switch (want) { > case 'LIST' { do_list_stu

Re: Change "($one, $two)=" behavior for optimization? (was Re: RFC 175 (v1) Add C keyword toforcelist context (like C))

2000-09-04 Thread Damian Conway
> > The LIST/SCALAR/VOID distinction is always the second value returned > > (see the examples in the RFC). So your dispatcher is: > > > > my $func = lc (want)[1] . "_func"; > > return &$func(@_); > > I think I'd much rather it be the first. This seems to jiv

Re: Change "($one, $two)=" behavior for optimization? (was Re: RFC 175 (v1) Add C keyword toforcelist context (like C))

2000-09-04 Thread Nathan Wiger
Damian Conway wrote: > > The LIST/SCALAR/VOID distinction is always the second value returned > (see the examples in the RFC). So your dispatcher is: > > my $func = lc (want)[1] . "_func"; > return &$func(@_); I think I'd much rather it be the first. This seems to jive much more