On Aug 20, 2005, at 20:12, Nicolas Cannasse wrote:
Hi list,
I tried to have a deeper look at Parrot so I installed latest PXPerl
with
Parrot 0.2.3 and I tried to run some benchmarks on my computer in
order to
compare with Neko.
I was thinking that Parrot JIT would outperform Neko VM easil
Hi,
Yuval Kogman woobling.org> writes:
> On Sat, Aug 20, 2005 at 22:27:56 +, Ingo Blechschmidt wrote:
> > > Not &code, but the return value of &code.emit
> >
> > Hm, Str? Or possibly a subtype of Str, allowing:
>
> I would guess an AST, that is, any object, that implements
> str
Output?
sub foo (+$a, *%overflow) {
say "%overflow{}";
}
foo(:a(1), :b(2)); # b2
foo(:a(1), :overflow{ b => 2 }); # b2
foo(:a(1), :overflow{ b => 2 }, :c(3)); # ???
Luke
Hi,
Luke Palmer wrote:
> sub foo (+$a, *%overflow) {
> say "%overflow{}";
> }
>
> foo(:a(1), :b(2)); # b2
> foo(:a(1), :overflow{ b => 2 }); # b2
I'd think so, too.
> foo(:a(1), :overflow{ b => 2 }, :c(3)); # ???
Error:
On Sun, Aug 21, 2005 at 12:11:17 +, Ingo Blechschmidt wrote:
> Hi,
>
> Yuval Kogman woobling.org> writes:
> But we should note that some backends don't generate meaningful
> ASTs, simply because they don't convert PIL -> target language
> AST -> target language, but PIL -> target langua
On Sat, Aug 20, 2005 at 10:33:03PM +, Ingo Blechschmidt wrote:
: Hi,
:
: S02 says:
: our $a; say $::("a"); # works
:
: my $a; say $::("a"); # dies, you should use:
: my $a; say $::("MY::a"); # works
That looks like somebody's relic of Perl 5 thinking. Personally
On 22/08/05, Luke Palmer <[EMAIL PROTECTED]> wrote:
> Output?
>
> sub foo (+$a, *%overflow) {
> say "%overflow{}";
> }
>
> foo(:a(1), :b(2)); # b2
> foo(:a(1), :overflow{ b => 2 }); # b2
I would have thought:
overflow b
On Fri, Aug 19, 2005 at 06:42:04PM +0300, Yuval Kogman wrote:
> If there is some really odd code signature which takes in a mess, I
> may want to intermix positionals and named's in order to increase
> readability.
AFAIR, named parameter syntax will work for positionals as well[*].
So even if you
