This works now:
$ cat hellow_world.txt
Hello world!
$ perl6-j -e 'say $*IN.get' < hello_world.txt
Hello world!
So this is closable with a test.
Hmm, it looks like that was not all -- or there is a new problem.
$ perl6-m -e 'for 42 {NEXT (state $val) = $_}; say "alive"'
alive
This does not fail any longer. But the tests in integration/advent2012-day15.t
don't pass. I'd say the following command shows more:
$ perl6-m -e 'for 42 {NEXT (st
The tests are now passing on JVM. I unfudged them with the following commit:
https://github.com/perl6/roast/commit/741b08ee70
# New Ticket Created by Christian Bartolomaeus
# Please include the string: [perl #123002]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=123002 >
I got a NullPointerException with a golfed version of a failing test from roast
Branch: refs/heads/master
Home: https://github.com/perl6/specs
Commit: a6c0bb79fb089b41497d80c55c7d71da115bb10a
https://github.com/perl6/specs/commit/a6c0bb79fb089b41497d80c55c7d71da115bb10a
Author: Elizabeth Mattijsen
Date: 2014-10-17 (Fri, 17 Oct 2014)
Changed paths:
Wouldn't "1,3,5,7" be a more reasonable result? The next value, "9" is
greater than the end term, so it should stop?
On 10/16/14, Carl Mäsak via RT wrote:
> bartolin (>):
>> Actually I don't think S03 says that '1,3,5 ... 8' should act as
>> '1,3,5 ... *'
>>
>> As I understand it '1,3,5 ... 8' gi
This works now:
$ perl6-m -e 'role R { method foo {}; R.foo }; say "alive"'
alive
$ perl6-p -e 'role R { method foo {}; R.foo }; say "alive"'
alive
$ perl6-j -e 'role R { method foo {}; R.foo }; say "alive"'
alive
I added a test to S14-roles/basic.t with the following commit:
https://github.c
This works on Moar but fails on Parrot and JVM:
$ perl6-m -e 'role A { method pub { self!priv }; method !priv () { say "OH HAI"
} }; class C does A { }; C.new.pub;'
OH HAI
$ perl6-p -e 'role A { method pub { self!priv }; method !priv () { say "OH HAI"
} }; class C does A { }; C.new.pub;'
Cannot
Status update: It looks like STD's opinion on this has changed:
$ viv -c -e 'sub a (:$b($c)) {say $c}; a(:b)'
===SORRY!===
Subsignature not allowed after named parameter; please insert whitespace at
(eval) line 1:
--> sub a (:$b⏏($c)) {say $c}; a(:b)
Parse failed
Rakudo's error messages are
This works fine with Moar and JVM, but is still an issue with Parrot:
$ perl6-m -e '%*ENV="foo"; say qx/env/ ~~ /ENV_TEST/' ## same
result with perl6-j
「ENV_TEST」
$ perl6-p -e '%*ENV="foo"; say qx/env/ ~~ /ENV_TEST/'
Nil
I added a test (fudged 'todo' for Parrot) to S02-literals/quoting.t with
To me it looks like the loop and the string concat are okay-ish (this is on a
"not too beefy" machine (i3 3.33 GHz, 8 GiB RAM):
$ perl6-m -e 'my $file = ""; for ^2 {$file ~= "$_;"};'
real0m0.500s
user0m0.436s
sys 0m0.060s
$ perl6-p -e 'my $file = ""; for ^2 {$file ~= "$_;"};
Status update: Right now this is no longer a Null PMC access error on Parrot
but we get a segfault on Moar as well:
$ perl6-m -e 'my $a ($b, $c); $b = 42;'
Segmentation fault
$ perl6-p -e 'my $a ($b, $c); $b = 42;'
Cannot assign to an immutable value
in block at -e:1
$ perl6-j -e 'my $a ($b,
This works for Moar, Parrot and JVM:
$ perl6 -e 'printf("%.50f", 1.115)'
1.115000
I added a test to S32-str/sprintf.t with the following commit:
https://github.com/perl6/roast/commit/46ef5bf0e9. I'm closing the ticket.
Since the current error message looks reasonable to me (though different from
STD's) I went ahead and added a test to S32-exceptions/misc.t with the
following commit: https://github.com/perl6/roast/commit/5265f7d69e
But: The new error message only happens with "my Int a;". Without the semicolon
I'm closing this ticket since this works now and there are tests in
S02-literals/heredocs.t (cmp. commit
https://github.com/perl6/roast/commit/978e4a8ac166821ab18a8c02c906063b6e489dd6)
$ perl6 -e 'say (EVAL "q:to/E/;\n\tfoo\n\tbar\n\tE") eq "foo\nbar\n"'
True
$ perl6 -e 'say (EVAL "q:to/E/;\n\t
15 matches
Mail list logo