Re: Nice Channel and thread example

Fixed with https://github.com/rakudo/rakudo/commit/91543fe310 , thanks for the report! > On 31 Oct 2017, at 00:32, Norman Gaywood wrote: > > Hmm, in developing this I was using an old perl6: > > This is rakudo version 2015.11-554-g3b4964b built on MoarVM version >

Re: Nice Channel and thread example

This also happens on HEAD, investigating... > On 31 Oct 2017, at 00:32, Norman Gaywood wrote: > > Hmm, in developing this I was using an old perl6: > > This is rakudo version 2015.11-554-g3b4964b built on MoarVM version > 2015.11-49-g27f15d9 implementing Perl v6.b. > > I

Re: Nice Channel and thread example

Hmm, in developing this I was using an old perl6: This is rakudo version 2015.11-554-g3b4964b built on MoarVM version 2015.11-49-g27f15d9 implementing Perl v6.b. I updated perl6 to the one that comes with Fedora: This is Rakudo version 2017.08 built on MoarVM version 2017.08.1 implementing Perl

Re: [perl #131846] [BUG] combinations not accepting Inf/Whatever as upper bound (Regression)

Fixed with bdc73563f484325cc544 , tests were already added, can be closed. > On 6 Aug 2017, at 17:13, Joshua (via RT) wrote: > > # New Ticket Created by Joshua > # Please include the string: [perl #131846] > # in the subject line of all future correspondence

Re: [perl #131846] [BUG] combinations not accepting Inf/Whatever as upper bound (Regression)

Fixed with bdc73563f484325cc544 , tests were already added, can be closed. > On 6 Aug 2017, at 17:13, Joshua (via RT) wrote: > > # New Ticket Created by Joshua > # Please include the string: [perl #131846] > # in the subject line of all future correspondence

[perl #132377] [BUG][POD] tables inside =begin/=end comment pairs cause exception

On Mon, 30 Oct 2017 09:16:23 -0700, tbrowder wrote: > On Mon, 30 Oct 2017 08:21:04 -0700, tbrowder wrote: > > On Mon, Oct 30, 2017 at 09:53 Elizabeth Mattijsen wrote: > > > > > A —ll-exception stacktrace would be useful in such a case :-) > > > > > > WILCO! $ cat prob.p6 use

[perl #132377] [BUG][POD] tables inside =begin/=end comment pairs cause exception

On Mon, 30 Oct 2017 08:21:04 -0700, tbrowder wrote: > On Mon, Oct 30, 2017 at 09:53 Elizabeth Mattijsen wrote: > > > A —ll-exception stacktrace would be useful in such a case :-) > > > WILCO! Expected "=end comment" to terminate "=begin comment"; found "=end table"

Re: [perl #132377] [BUG][POD] tables inside =begin/=end comment pairs cause exception

On Mon, Oct 30, 2017 at 09:53 Elizabeth Mattijsen wrote: > A —ll-exception stacktrace would be useful in such a case :-) WILCO!

Re: [perl #132377] [BUG][POD] tables inside =begin/=end comment pairs cause exception

On Mon, Oct 30, 2017 at 09:53 Elizabeth Mattijsen wrote: > A —ll-exception stacktrace would be useful in such a case :-) WILCO!

Re: [perl #132377] [BUG][POD] tables inside =begin/=end comment pairs cause exception

A —ll-exception stacktrace would be useful in such a case :-) > On 30 Oct 2017, at 15:24, Tom Browder (via RT) > wrote: > > # New Ticket Created by Tom Browder > # Please include the string: [perl #132377] > # in the subject line of all future correspondence

Re: [perl #132377] [BUG][POD] tables inside =begin/=end comment pairs cause exception

A —ll-exception stacktrace would be useful in such a case :-) > On 30 Oct 2017, at 15:24, Tom Browder (via RT) > wrote: > > # New Ticket Created by Tom Browder > # Please include the string: [perl #132377] > # in the subject line of all future correspondence

[perl #132377] [BUG][POD] tables inside =begin/=end comment pairs cause exception

# New Ticket Created by Tom Browder # Please include the string: [perl #132377] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132377 > The following pod causes an exception =begin comment =begin table a | b | c =end table

Re: [perl #132353] [LTA] error with using meta assign ops with bound SetHash

Fixed with b6a4d5b20451c5c8a, this now DWIM, tests needed. Error message being too long, fixed with 497e0582e6c64ccc04b2e9 . > On 23 Oct 2017, at 14:28, Zoffix Znet (via RT) > wrote: > > # New Ticket Created by Zoffix Znet > # Please include the string:

Re: [perl #132353] [LTA] error with using meta assign ops with bound SetHash

Fixed with b6a4d5b20451c5c8a, this now DWIM, tests needed. Error message being too long, fixed with 497e0582e6c64ccc04b2e9 . > On 23 Oct 2017, at 14:28, Zoffix Znet (via RT) > wrote: > > # New Ticket Created by Zoffix Znet > # Please include the string:

Re: [perl #132352] Set operators unfriendly to mutable types

> On 24 Oct 2017, at 12:56, Zoffix Znet via RT > wrote: > On Mon, 23 Oct 2017 09:12:58 -0700, sml...@gmail.com wrote: >> On Mon, 23 Oct 2017 05:23:55 -0700, c...@zoffix.com wrote: >> The "solution", IMO, would not be to make your quoted example work (by >> adding

Re: [perl #132352] Set operators unfriendly to mutable types

> On 24 Oct 2017, at 12:56, Zoffix Znet via RT > wrote: > On Mon, 23 Oct 2017 09:12:58 -0700, sml...@gmail.com wrote: >> On Mon, 23 Oct 2017 05:23:55 -0700, c...@zoffix.com wrote: >> The "solution", IMO, would not be to make your quoted example work (by >> adding

Re: How do I read a pipe into a one liner?

On 10/29/2017 11:18 PM, ToddAndMargo wrote: Dear List, I am trying to translate this P5 coder to P6. I am looking at how to read a pipe into a line liner: ReadAPipe.pl #!/usr/bin/perl use strict; use warnings; chomp(my $Pipe = ( ! -t \*STDIN ) ? do{local $/; } : q{}); print "This was read

How do I read a pipe into a one liner?

Dear List, I am trying to translate this P5 coder to P6. I am looking at how to read a pipe into a line liner: ReadAPipe.pl #!/usr/bin/perl use strict; use warnings; chomp(my $Pipe = ( ! -t \*STDIN ) ? do{local $/; } : q{}); print "This was read from the pipe:\n<$Pipe>\n\n"; print "These