Christian Soeller wrote:
> Dan Sugalski wrote:
>
> >
> > Because source filters are:
> >
> > 1) Relatively new (5.005 IIRC, but I could be mis-remembering)
> > 2) A bloody pain in the neck to write
> >
> > Lots of things could use 'em if they were easier to do. That's one of the
> > goals of perl
>
>
> Regardless, you can already do this in perl 5, and will undoubtedly be able
> to do it in perl 6, with source filters.
So why do we have to do
$ip1=$i+1;# my pdl pet peave
$f->slice("(0),$ip1,$i");
instead of
$f((0),$i+1,$i); # substitute your favorite syntax
IMHO if the perl6 core only allow access to the parser, than a module can do just
about anything including all of those things proposed in RFC 115 - 117.
Maybe this is an over simplification, but it seems that if the statement:
use Python;
caused the subsequent source to go through my Python:
Baris wrote:
> Hi,
> > ^foo = ([1, 2], [3, 4]); # I know, it's taken, I helped :-)
> > $foo[0,0];# uh-oh
> >
> >Then adding a new fundamental type and syntax is not only unnecessary,
> >but silly.
>
> Why do you think that individual elements are perl scalars? since w
Tom Christiansen wrote:
> printf "uid %d logged on from %s on %s.\n",
> $him->ut_uid, $him->ut_host, scalar local $him->ut_date;
>
>
Is ut_uid a scaler value here? It occured to me when I read this that it would
be nice to get rid of the distinction between
$him->{ut_uid}
$him->[ut
