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

2016-09-19 Thread Elizabeth Mattijsen
This is a dup of #129304, which has been fixed with c78f5dc7df5b1398d2867 , tests needed. > On 19 Sep 2016, at 01:00, Benjamin Goldberg (via RT) > wrote: > > # New Ticket Created by Benjamin Goldberg > # Please include the string: [perl #129305] > # in the subject line of all future corresp

Re: [perl #129304] [REGRESSION] .first with a junction unexpectedly returns a junction (.first: ā€˜a’|ā€˜c’)

2016-09-19 Thread Elizabeth Mattijsen
Fixed with c78f5dc7df5b1398d2867 , tests needed. > On 19 Sep 2016, at 00:46, Aleks-Daniel Jakimenko-Aleksejev (via RT) > wrote: > > # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev > # Please include the string: [perl #129304] > # in the subject line of all future correspondence abou

[perl #129307] [BUG] $/.perl doesn't round-trip when captures are present

2016-09-19 Thread via RT
# New Ticket Created by Zoffix Znet # Please include the string: [perl #129307] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129307 > The S05-match/perl.t contains this test: is-deeply EVAL($/.perl), $/, 'EVAL of Match

Re: Is this a bug?

2016-09-19 Thread Aaron Sherman
I'm guessing that what you meant was "say as a function was what I meant to use there." In which case: say for reverse lines or for reverse lines { say } These are both valid ways of asking for each element of the iterable thing returned from lines to be printed with a newline. But remember th

Re: This seems to be wrong

2016-09-19 Thread Aaron Sherman
"for @inputs.map( .prefix:<+> ) {...}" That's spelled: "for @inputs>>.Int -> $i { ... }" You can also use map, but it's slightly clunkier: "for @inputs.map: .Int -> $i { ... }" Aaron Sherman, M.: P: 617-440-4332 Google Talk, Email and Google Plus: a...@ajs.com Toolsmith, developer, gamer and

Re: This seems to be wrong

2016-09-19 Thread Timo Paulssen
On 19/09/16 15:56, Aaron Sherman wrote:> You can also use map, but it's slightly clunkier: > > "for @inputs.map: .Int -> $i { ... }" This also needs to have "*.Int" or "{ .Int }" otherwise you'll pass $_.Int as the argument to map rather than telling map to call .Int on things.

Re: Is this a bug?

2016-09-19 Thread Timo Paulssen
On 19/09/16 16:02, Aaron Sherman wrote: > I'm guessing that what you meant was "say as a function was what I > meant to > use there." In which case: > > say for reverse lines > > or > > for reverse lines { say } > > These are both valid ways of asking for each element of the iterable > thing retur

Re: Is this a bug?

2016-09-19 Thread Parrot Raiser
It may make it clearer if I explain the broader objective. I'm trying to learn P6 thoroughly by developing training courses to teach it from scratch. (Fans of Gerald Weinberg may recognise the idea.) Obviously, while doing so, I want to explore pathological cases, both to clarify the concepts and t

Re: Is this a bug?

2016-09-19 Thread Aaron Sherman
Thank you. Silly me, thinking "this is so simple I don't need to run it through the command-line to test it." :-) Anway, yeah, say $_ for reverse lines Aaron Sherman, M.: P: 617-440-4332 Google Talk, Email and Google Plus: a...@ajs.com Toolsmith, developer, gamer and life-long student.

[perl #127967] [JVM] Test in S06-advanced/wrap.t dies with "control operator crossed continuation barrier"

2016-09-19 Thread Christian Bartolomaeus via RT
On Sat Apr 23 01:51:35 2016, barto...@gmx.de wrote: > The following code (from S06-advanced/wrap.t, test skipped for rakudo- > j) dies on rakudo-jvm: > > $ perl6-j -e 'my @t = gather { sub triangle { take "=" x 3; }; for > reverse ^3 -> $n { &triangle.wrap({ take "=" x $n; callsame; take "=" > x $

[perl #125331] [BUG] Match on undefined value returns twodifferent warning messages

2016-09-19 Thread Will Coleda via RT
On Fri Jun 05 02:00:55 2015, ppab...@implix.com wrote: > $ perl6 -e 'loop { $_ ~~ /.+/ }' > > While it runs two different error messages are returned: > > 1. Use of uninitialized value of type Any in string context in block > at -e:1 > 2. Use of uninitialized value of type Any in string context

[perl #127215] Negative codepoint in .comb + /:m/

2016-09-19 Thread Will Coleda via RT
On Fri Jan 08 21:03:49 2016, ju...@tnx.nl wrote: > $ perl6 -e'say "hello".comb(/:m <[o]>/)' > ===SORRY!=== > chr codepoint cannot be negative > -- Will "Coke" Coleda I can no longer duplicate this: $ perl6 --version This is Rakudo version 2016.08.1 built on MoarVM version 2016.08