[perl #130775] [JVM] Problems with 'with' and attached block

2017-02-14 Thread Christian Bartolomaeus via RT
I think I know what happens. On MoarVM we call the Perl 6 method 'defined': https://github.com/perl6/nqp/blob/ac9a66abad13a7fd3d52b22ba533a9f8436ad1ac/src/vm/moar/QAST/QASTOperationsMAST.nqp#L787 On JVM we test for concreteness (like nqp::isconcrete would do): https://github.com/perl6/nqp/blob/

[perl #125757] shell().exitcode is always 0 when :out is used

2017-02-14 Thread Zoffix Znet via RT
On Thu, 18 Feb 2016 09:51:34 -0800, ug...@cpan.org wrote: > The assignment fix can be simplified further: > $ perl6 -e 'my $p = shell("false", :out); |$p.out.close; say > $p.exitcode' > 1 Or even simpler: $ perl6 -e 'my $p = shell("false", :out); $p.out.close.exitcode.say' 1 .close doesn

[perl #130786] [32BIT] unhandled Failure detected in DESTROY

2017-02-14 Thread Zoffix Znet via RT
Just realized something: I fixed Str ~~ Numeric to not throw, so on HEAD there won't be any Failures at all with the sample code. I tried changing the tests to use $a + $b instead of $a ~~ $b, but then the DESTROY warning does not occur... ... should this ticket be closed?

[perl #130786] [32BIT] unhandled Failure detected in DESTROY

2017-02-14 Thread via RT
# New Ticket Created by Zoffix Znet # Please include the string: [perl #130786] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=130786 > The Failure has DESTROY submethod[^1] with a comment above it saying "Shouldn't happen".

[perl #130715] IO::Handle::close shouldn't decide what's a failure

2017-02-14 Thread Zoffix Znet via RT
On Mon, 13 Feb 2017 21:04:37 -0800, raiph wrote: > This comment is technically redundant. And maybe not helpful. I > apologize if it's annoying to anyone. Not annoying, but I feel we all have thoroughly confused bdfoy by now :P Some minor corrections: > 4.1 `sink some.expression;` > > In stark

[perl #130761] An if-block confuses &?ROUTINE to point at the wrong outer routine

2017-02-14 Thread Zoffix Znet via RT
On Sat, 11 Feb 2017 03:29:18 -0800, moritz wrote: > sub f($x) { > sub { > if True { > say &?ROUTINE.name > } > } > }.(42)() > > This prints f on Rakudo 2017.01-170-gc0a907f built on MoarVM version > 2017.01-31-g20dfa6b > > &?ROUTINE sh

Re: [perl #130776] Environment variables are case insensitive on Windows

2017-02-14 Thread A. Sinan Unur
I am not sure what the right strategy is ... Perl 5 seems to work mainly because they use the ANSI interfaces to get environment variables ... which means you can't get the value of $ENV{iş}. I opened this issue because I am going to think about it and thought there should be something to referenc

[perl #130776] Environment variables are case insensitive on Windows

2017-02-14 Thread Zoffix Znet via RT
On Mon, 13 Feb 2017 14:38:03 -0800, na...@cpan.org wrote: > $ echo %windir% > C:\WINDOWS > > $ echo %WINDIR% > C:\WINDOWS > > $ c:\opt\perl6-mingw\bin\perl6 -e "say %*ENV" > (Any) > > $ c:\opt\perl6-mingw\bin\perl6 -e "say %*ENV" > C:\WINDOWS > > $ c:\opt\perl6-mingw\bin\perl6 -v > This is Raku

[perl #130776] Environment variables are case insensitive on Windows

2017-02-14 Thread Zoffix Znet via RT
On Mon, 13 Feb 2017 14:38:03 -0800, na...@cpan.org wrote: > $ echo %windir% > C:\WINDOWS > > $ echo %WINDIR% > C:\WINDOWS > > $ c:\opt\perl6-mingw\bin\perl6 -e "say %*ENV" > (Any) > > $ c:\opt\perl6-mingw\bin\perl6 -e "say %*ENV" > C:\WINDOWS > > $ c:\opt\perl6-mingw\bin\perl6 -v > This is Raku