Uri,
On Sun, 04 Jan 2009 22:37:43 -0500, Uri Guttman wrote:
> that fails with nested arrays. we don't want them to flatten.
>
> my $c = eval '(1, (4, 5), 3)';
>
> will that work as you envision?
No, but it's not what I'm proposing. A reference must Perlify as a
reference, just as it does toda
On Sun, 04 Jan 2009 14:19:15 -0500, Uri Guttman wrote:
>> "m" == moritz writes:
> m> But I think that a .perl()ification as ("blue", "light", "hayard",) would
> m> make much more sense, because simple thing like
>
> m> @a.push eval(@b.perl)
>
> m> would then DWIM.
>
> for your def
This behaviour looks wrong to me:
m...@edward:~/perl/6$ cat ap1
#!/home/msl/bin/perl6
my @a = ;
my $p = @a.perl;
say "\...@a: {...@a.elems} elements: $p";
say '@a[0]: ', @a[0];
my @b = eval $p;
say "\...@b: {...@b.elems} elements: $p";
say '@b[0]: ',@b[0];
say '@b[0][0]: ', @b[0][0];
m...@
If I've got this right:
mangle $foo :a;# mangle($foo, a => 1);
mangle $foo: a;# $foo.mangle(a());
So these --
mangle $foo:a;
mangle $foo : a;
are ambiguous and, as far as I can tell from the synopses, undefined. So
what's the rule: that indirect-object colon needs whitespace after but
