bri (>):
> So this might be a closeable ticket now?
Yes, I would say so. Good work.
Resolving.
Fresher test results: no duplicate warnings, NULL pointers in REPL
under parrot and jvm but not moar. Probably LTA to be telling the
user to use '0o8' or '0o9'.
NOTE: my perl6-p is Star.2014.12 and my perl6-j/m are built from star-daily
Cologne-256-gd78c678.
$ perl6-p -e 'say 09'
Potential diff
Now STD does not parse "do...while" anymore, and there
are tests to ensure rakudo does not parse "do...while"
either, and tests to ensure the "repeat...while" and
"repeat...until" forms work, as well.
S04-statements/repeat.t
S04-statements/do.t
So this might be a closeable ticket now?
The test in S06-signature/introspection.t is passing (for quite a while, I
guess). I'm closing this ticket now.
The test passes now and was unfudged with commit
https://github.com/perl6/roast/commit/4954d43df4
I'm closing this ticket now. (whoever fixed this)++
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #123709]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=123709 >
m: sub &foo() {}; say "alive"
rakudo-moar 6e182d: OUTPUT«===SORRY!=== Error while
compi
On Sat Jan 24 13:52:59 2015, barto...@gmx.de wrote:
> As a status update: I don't get a segfault in the REPL with a current
> rakudo (tested on moar, parrot and jvm).
>
> The error message has changed slightly:
More exactly, the segfault is now gone.
m: class Foo { has Hash of Hash $.foo = {} }
