Chris (>):
> How safe is it today to pre-compile Rakudo code to PIR and expect that to
> behave identically to as if I compiled from .pm at runtime? I believe PCT
> is just generating PIR anyway, so my initial guess is that there should be
> no differences. Are there any gotchas, like compile-tim
On Oct 27, 2008, at 3:07 AM, Carl Mäsak wrote:
Chris (>):
How safe is it today to pre-compile Rakudo code to PIR and expect
that to
behave identically to as if I compiled from .pm at runtime? I
believe PCT
is just generating PIR anyway, so my initial guess is that there
should be
no diffe
On Sun, Oct 26, 2008 at 10:45 PM, Chris Dolan <[EMAIL PROTECTED]> wrote:
> S05 always uses single curlies for closures, but throughout Parrot, code
> seems to use double curlies in PGE regexps. Why is that?
>
> That is, why this:
> m/ foo {{ say "found foo" }} /
> and not this:
> m/ foo { say "f
On Sat, Oct 25, 2008 at 10:52:13AM +0200, Moritz Lenz wrote:
> Chris Dolan wrote:
> > I stumbled across this issue while descending into a recursive Match
> > structure. Consider the following reentrant subroutine:
>
> You have just experienced this bug:
> http://rt.perl.org/rt3/Ticket/Display.
