# New Ticket Created by David Golden
# Please include the string: [perl #60116]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60116 >
As per the subject, the t/harness program should exit with a non-zero
value on test fail
# New Ticket Created by chromatic
# Please include the string: [perl #60124]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60124 >
I expect this code to dispatch properly; autoboxing works and :optional
parameters work, a
On Sun, Oct 26, 2008 at 2:00 AM, via RT Will Coleda
<[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Will Coleda
> # Please include the string: [perl #60128]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=60128 >
>
>
>
# New Ticket Created by James Keenan
# Please include the string: [perl #60134]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60134 >
We've had file-based configuration since r30640 (2008-08-29). I was
prompted by some
Work completed and merged into trunk in r32182.
As a funny bonus, Parrot segfaults if the dummy assignment is left out
inside the loop:
$
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #60150]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60150 >
Rakudo r32151 is only able to call &-sigil subs if they have not been
initialized with "
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #60144]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60144 >
Rakudo r32141 fails to accept undef as a value to typed variables.
$ ./perl6 -e 'my Int
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #60140]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60140 >
Rakudo r32151 reads one line in a for loop, and then exits the loop.
$ ./perl6 -e '.say
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #60142]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60142 >
Rakudo r32151 contains a bug which makes it "read" a nonexistent blank
line at the end o
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #60148]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60148 >
Rakudo r32141 can understand unspaces consisting of a backslash
followed by whitespace,
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #60152]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60152 >
rakudo: if(3 < 5) { say "yes" } # that should fail
rakudo 31963: OUTPUT[yes]
moritz_
From: chromatic (via RT) <[EMAIL PROTECTED]>
Date: Sat, 25 Oct 2008 18:21:26 -0700
# New Ticket Created by chromatic
# Please include the string: [perl #60124]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id
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-time dependenc
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 "found foo" } /
The latter complains about "Statement not terminated properly".
C
15 matches
Mail list logo
