Hi Mikhail,
I was unable to reproduce the segmentation fault with current rakudo.parrot:
$ (cd Pod-SAX/; git log -n 1)
commit 80e45173429c493f0a8ffe5f667ada51917e195d
Author: Mikhail Khorkov
Date: Sat Jul 12 01:13:22 2014 +0700
Save state with SIGSEGV
Save state with SIGSEGV.
$
S03-operators/overflow.t passes now on rakudo.parrot on cygwin (64-bit):
cygwin$ perl6-p t/spec/S03-operators/overflow.t
1..98
ok 1 - var incremented after post-autoincrement
ok 2 - during post-autoincrement return value is not yet incremented
ok 3 - var incremented after pre-autoincrement
ok 4 -
Looks like ~~:z returns True on directories now:
cygwin> perl6-p t/spec/S16-filehandles/filetest.t
1..43
ok 1 - file test from before spec revision 27503 is error
ok 2 - ~~:d returns true on directories
ok 3 - can :d-test against non-existing dir and live
ok 4 - can :d-test against non-existing di
This works now (was fixed with Parrot 6.10.0; cmp.
https://github.com/parrot/parrot/blob/master/ChangeLog#L30):
cygwin> perl6-p t/spec/S19-command-line/dash-e.t
1..4
ok 1 - -e print $something works
ok 2 - -e print $something works with non-ASCII string literals
ok 3 - -e works with non-ASCII pro
# New Ticket Created by David Warring
# Please include the string: [perl #123276]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=123276 >
Consider three simple classes:
lib/A.pm:
class A {}
lib/A/B/C1.pm:
class A::B::C1 { us
This now emits a warning about useless use of "," in sink context, but the
result hasn't changed:
$ perl6 -e 'my @foo; @foo ,= 1, 2, 3; @foo.perl.say'
WARNINGS:
Useless use of "," in expression ",= 1, 2, 3" in sink context (line 1)
Array.new(1)
I added a test (fudged "todo") to S03-operators/ass
