Re: [perl #129296] Regression: splitting non-binary handles no longer works

Fixed by reverting 1a03efe4e3b61a07b7df5 in 363a3a899f2cb342d1ca5 . > On 18 Sep 2016, at 05:19, Aleks-Daniel Jakimenko-Aleksejev (via RT) > wrote: > > # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev > # Please include the string: [perl #129296] > # in the subject line of all future

[perl #129299] [REGEX] Quantified capture group breaks `$/.list`

# New Ticket Created by Sam S. # Please include the string: [perl #129299] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129299 > When a quantified capture group matched zero times but the overall regex matches, then the Lis

Is this a bug?

This code: 1 #! /home/guru/bin/perl6 2 3 # Ask for some lines and output them in reverse 4 # Work out the appropriate EOF symbol for the OS 5 6 my $EOF = "CTRL-" ~ ($*DISTRO.is-win ?? "Z" !! "D"); 7 8 say "Please enter some lines and end them with $EOF"; 9 10 say { for reverse lines() {} }; 11 12 #

Re: Is this a bug?

I think you want: .say for reverse lines; not sure what you are trying to achieve otherwise, but: say { } producing something like -> ;; $_? is raw { #`(Block|170303864) … } feels entirely correct to me. :-) Liz > On 18 Sep 2016, at 21:52, Parrot Raiser <1parr...@gmail.com> wrote

This seems to be wrong

This code: #! /home/guru/bin/perl6 # Ask for some numbers from 1 - 7 # and verify that they are in range my @names = < fred betty barney dino wilma pebbles bamm-bamm >; my @inputs = lines(); for @inputs { if $_ ~~ 1..7 { say @names[$_-1]; } else { say "$_ out of r

Re: Is this a bug?

Remember you can call a block with parentheses: > say { 11 + 31 }; -> ;; $_? is raw { #`(Block|140268472711224) ... } > say { 11 + 31 }(); 42 On Sun, Sep 18, 2016 at 12:58 PM, Elizabeth Mattijsen wrote: > I think you want: > > .say for reverse lines; > > not sure what you are trying to achie

Re: This seems to be wrong

On Sun, Sep 18, 2016 at 4:31 PM, Parrot Raiser <1parr...@gmail.com> wrote: > but seems to have a problem with larger numbers: > > 7 > 3 > 21 <- This > 2 > 1 > 0 > 4 > bamm-bamm > barney > (Any) <--- Produces this > betty > fred > 0

Re: [perl #129299] [REGEX] Quantified capture group breaks `$/.list`

I’m looking into this. This appears to be an artefact of .gist on the list, caused by the say. Which also happens for .perl on the list. say $/.list.Str; # a c Suspecting the gistseen/perlseen machinery now. Investigating... > On 18 Sep 2016, at 19:30, Sam S. (via RT) > wrote: >

Re: Is this a bug?

say { $_ } was the correct thing to use there. (I'm trying to avoid any mention of O-O for the moment.) say {} was a "what happens if I do this" exercise. What is this -> ;; $_? is raw { #`(Block|170303864) … } output? On 9/18/16, Brent Laabs wrote: > Remember you can call a block with parenthe

Re: Is this a bug?

It is the .perl representation of a Block. > On 18 Sep 2016, at 22:49, Parrot Raiser <1parr...@gmail.com> wrote: > > say { $_ } was the correct thing to use there. (I'm trying to avoid > any mention of O-O for the moment.) > say {} was a "what happens if I do this" exercise. > > What is this ->

Re: Is this a bug?

On Sun, Sep 18, 2016 at 4:49 PM, Parrot Raiser <1parr...@gmail.com> wrote: > What is this -> ;; $_? is raw { #`(Block|170303864) … } output? It's the gist of a Block, which is what you asked for when you did a `say` on an executable block. Why do you believe `say { $_ }` is the right thing ther

Re: [perl #129299] [REGEX] Quantified capture group breaks `$/.list`

Ah, found it: The List iterator assumes that a List cannot have “holes” in it. Apparently it can :-( Going to sleep on how to fix this. > On 18 Sep 2016, at 19:30, Sam S. (via RT) > wrote: > > # New Ticket Created by Sam S. > # Please include the string: [perl #129299] > # in the subjec

Re: [perl #129299] [REGEX] Quantified capture group breaks `$/.list`

Fixed (for now at least) with 9b6f2eb5434e71f07bc649 . Tests still needed. > On 18 Sep 2016, at 19:30, Sam S. (via RT) > wrote: > > # New Ticket Created by Sam S. > # Please include the string: [perl #129299] > # in the subject line of all future correspondence about this issue. > # https:

Re: This seems to be wrong

On Sun, Sep 18, 2016 at 6:06 PM, Trey Harris wrote: > Not work? It results inMethod 'prefix:<+>' not found for invocant of > class 'Any', but the docs > > > say it is defined as a multi on Any…. > > No, they say it's a multi sub, not a multi me

Re: This seems to be wrong

On Sun, Sep 18, 2016 at 6:15 PM, Brandon Allbery wrote: > for @inputs.map({ .&prefix:<+> }) { ... } Which means the shorter way is: for @inputs.map(+*) { ... } -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com

Re: This seems to be wrong

Why does this: for @inputs.map( .prefix:<+> ) { ... } Not work? It results inMethod 'prefix:<+>' not found for invocant of class 'Any', but the docs say it is defined as a multi on Any…. Trey ​ On Sun, Sep 18, 2016 at 4:37 PM Brandon Allbery

Re: This seems to be wrong

On Sun, Sep 18, 2016 at 6:29 PM, Trey Harris wrote: > But I see there’s a multi method Str defined on Any, and you can’t do > @inputs.map( .Str ), either (Use of uninitialized value $_ of type Any in > string context). Why not? (There’s no multi method Num on Any, even > though the docs about Coo

Re: Is this a bug?

On Sun, Sep 18, 2016 at 16:49 Parrot Raiser <1parr...@gmail.com> wrote: say { $_ } was the correct thing to use there. (I'm trying to avoid > any mention of O-O for the moment.) > “Trying to avoid any mention of O-O” seems like a Perl 6 obfuscation or golf constraint, not a desirable development o

Re: This seems to be wrong

On Sun, Sep 18, 2016 at 6:36 PM, Trey Harris wrote: > Does not being defined on Any explain why the error for @input.map( .Str ) > is different (Use of uninitialized value $_ of type Any in string context) > than the error for @input.map( .Num ) (Method 'Num' not found for > invocant of class 'An

[perl #129304] [REGRESSION] .first with a junction unexpectedly returns a junction (.first: ‘a’|‘c’)

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #129304] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129304 > Differences between 2015.12 and HEAD: committable6: 2015.12,HEAD .f

[perl #129305] [BUG] .first autothreads when the matcher is a Junction

# New Ticket Created by Benjamin Goldberg # Please include the string: [perl #129305] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129305 > Here is a snippet from #perl6 on freenode: m: ('a', 42, 'b', 22/7, 'c', 23).first(

[perl #129306] [LTA] “cannot stringify this” error message if the signature is incorrect ( sub foo(@array ($first, @rest)) )

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #129306] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129306 > Code: sub foo(@array ($first, @rest)) { say @rest }; foo <1 2 3> Res

Re: This seems to be wrong

D’oh! I’m blind. But I see there’s a multi method Str defined on Any, and you can’t do @inputs.map( .Str ), either (Use of uninitialized value $_ of type Any in string context). Why not? (There’s no multi method Num on Any, even though the docs about Cool seem to

Re: This seems to be wrong

On Sun, Sep 18, 2016 at 6:30 PM Brandon Allbery allber...@gmail.com wrote: > On Sun, Sep 18, 2016 at 6:29 PM, Trey Harris wrote: > >> But I see there’s a multi method Str defined on Any, and you can’t do >> @inputs.map( .Str ), either (Use of uninitialized val