Howdy,
I am pleased to announce a new mailing list for PL/Parrot [0]
development and news. PL/Parrot aims to add PosgreSQL Languages (PL's)
for languages that Parrot [1] speaks. At first, this will be PIR
(Parrot Intermediate Representation) [2]. Once PIR is well supported,
then languages implemen
Please find:
http://lith-ology.blogspot.com/2010/01/seven-days-between-parrot-and-camel_15.html
Lithos
___
http://lists.parrot.org/mailman/listinfo/parrot-dev
Vasily Chekalkin wrote:
> Moritz Lenz wrote:
>>
>> Rakudo doesn't build on parrot HEAD since the CallSignature +
>> CallContext merge (or whatever it was called), so it's kinda hard to
>> figure out if there are any parrot bugs affecting Rakudo.
>
> Try this patch. It should work.
I've tested it
Vasily Chekalkin wrote:
> Moritz Lenz wrote:
>>
>> Rakudo doesn't build on parrot HEAD since the CallSignature +
>> CallContext merge (or whatever it was called), so it's kinda hard to
>> figure out if there are any parrot bugs affecting Rakudo.
>
> Try this patch. It should work.
Thanks. I'll t
Moritz Lenz wrote:
Rakudo doesn't build on parrot HEAD since the CallSignature +
CallContext merge (or whatever it was called), so it's kinda hard to
figure out if there are any parrot bugs affecting Rakudo.
Try this patch. It should work.
--
Bacek
diff --git a/src/binder/bind.c b/src/binder/
chromatic wrote:
> Hello everyone,
>
> Parrot 2.0 will come out in less than a week, and I'd like to make sure that
> Rakudo #25 will work well with it. What's the current status, and are there
> any bugs or errors that need addressing before the release?
Rakudo doesn't build on parrot HEAD si
Hello everyone,
Parrot 2.0 will come out in less than a week, and I'd like to make sure that
Rakudo #25 will work well with it. What's the current status, and are there
any bugs or errors that need addressing before the release?
-- c
___
http://lists
