On Sat, Apr 07, 2012 at 07:12:19PM -0700, Allison Randal wrote:
> Patrick and I just chatted on the phone, here's a summary of the working
> scenario we reached:
>
> - Rakudo will deliver a Rakudo release for each supported ("stable")
> Parrot release, a few days after the Parrot release.
>
> - D
Branch: refs/heads/master
Home: https://github.com/perl6/specs
Commit: 62f3a4ba1785a3d6b0adc4a4e7648f91300a7d31
https://github.com/perl6/specs/commit/62f3a4ba1785a3d6b0adc4a4e7648f91300a7d31
Author: Herbert Breunung
Date: 2012-04-07 (Sat, 07 Apr 2012)
Changed paths:
M S
On Sat, Apr 07, 2012 at 03:24:37PM -0700, Allison Randal wrote:
> These are things that Rakudo shouldn't care about. A bug-fix or
> performance enhancement in Parrot is good, but doesn't actually affect
> Rakudo's ability to build or run.
Sometimes it does. See the flurry of difficulties we had l
On 4/7/2012 19:11, Allison Randal wrote:
Okay, instead of just complaining about this, I want to do something
about it. The Rakudo packages are so fragile on Debian, that they need
special constraints to make sure the Parrot packages are held back until
the Rakudo packages are updated.
So, why i
heres my rationale.
i like the cute idea to name the special var like the general quoting op,
but no other var of that family does that (it goes bit like tamian rational
for $*pod). $~Q is just not descipive as $~Regex, which should be $~rx then,
or than should be $~Trans => $~tr and $~MAIN or $~Q
