# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #66928]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=66928 >
rakudo: say &infix:<+>.WHAT
rakudo 0e0671: OUTPUT«Null PMC access in find_method() [..
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #66926]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=66926 >
rakudo: say &infix:<+>
rakudo 0e0671: OUTPUT«10»
why is this giving 10 with no args?
I don't have any idea where the problem might be; since the Rakudo team
doesn't build the packages you installed I'm not quite sure where to
being troubleshooting.
I suggest contacting the packager who put together the binaries; try
with the latest Rakudo release; or see if you can build Rakudo fr
This was caused by a bug in Parrot; the problem in Parrot seems to have
been resolved and now EOF appears to work again.
Closing ticket, thanks!
Pm
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #66948]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=66948 >
Congratulations! This is the 400th new/open bug in the RT queue!
rakudo: [+]
rakudo 0
On Tue Jun 16 10:14:11 2009, richardh wrote:
> my @a=1,2,3,4; my @b=9,8,7,1; say (@a minmax @b).perl
While rakudo doesn't implement infix: yet, the operator is
constrained to having two elements on either side, so the above code
wouldn't work anyway.
It would be good to have some tests for infix:
This is a Parrot bug. Recently the Parrot team have been working to
clean up memory leaks in context handling, and as a result we're
starting to see "double free" errors on exit again. Running Rakudo with
Parrot's -G flag avoids the backtrace.
I'll leave this ticket open for now but mark it as "
