This looks good now: It doesn't die anymore, but returns "foo bar".
$ perl6-m -e '$_ = "foo bar"; say m/ "{ $_ }" /'
｢foo bar｣
$ perl6-p -e '$_ = "foo bar"; say m/ "{ $_ }" /'
｢foo bar｣
$ perl6-j -e '$_ = "foo bar"; say m/ "{ $_ }" /'
｢foo bar｣
I added a test to S05-mass/rx.t with the following
This looks better now:
$ perl6-m foo
Could not open foo. Failed to open file: no such file or directory
$ perl6-p foo
Could not open foo. Unable to open filehandle from path 'foo': No such file or
directory(2)
$ perl6-j foo
Could not open foo. java.nio.file.NoSuchFileException: foo
So, I'd say c
As FROGGS pointed out on IRC
(http://irclog.perlgeek.de/perl6/2014-10-07#i_9469198) the behaviour on Parrot
is not exactly as last year. I did a fresh build and now I get the "Null PMC
access" errors only when putting the declaration in an extra block. (That's
what happening in my tests where I
Branch: refs/heads/master
Home: https://github.com/perl6/specs
Commit: 148469ce7a5a9c1527017a7d77a664331b534477
https://github.com/perl6/specs/commit/148469ce7a5a9c1527017a7d77a664331b534477
Author: Elizabeth Mattijsen
Date: 2014-10-07 (Tue, 07 Oct 2014)
Changed paths:
Branch: refs/heads/master
Home: https://github.com/perl6/specs
Commit: e7593f051006bdadd85998ba451ced68482f8e0d
https://github.com/perl6/specs/commit/e7593f051006bdadd85998ba451ced68482f8e0d
Author: Elizabeth Mattijsen
Date: 2014-10-07 (Tue, 07 Oct 2014)
Changed paths:
On Moar and on JVM all of those declarations run fine. On Parrot the errors are
still the same. I added tests (fudged for Parrot) for two of the different
declarations to S06-operator-overloading/sub.t with the following commit:
https://github.com/perl6/roast/commit/dea36c4818
Hi,
this works now (probably for a while, already). I added a test to
S04-declarations/constant.t with the following commit:
https://github.com/perl6/roast/commit/6cc8c38a1c
Please note: If you smart match agains a regex you don't get a boolean value
but either a Match object or Nil:
> ("foo"
