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
> 2015.11-49-g27f15d9 implemen
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 updated perl6 to the
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
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 about this issue.
> # https://rt.
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 about this issue.
> # https://rt.
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 v6;
# an empty ta
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" instead.
at SETTING::s
On Mon, Oct 30, 2017 at 09:53 Elizabeth Mattijsen wrote:
> A —ll-exception stacktrace would be useful in such a case :-)
WILCO!
On Mon, Oct 30, 2017 at 09:53 Elizabeth Mattijsen wrote:
> A —ll-exception stacktrace would be useful in such a case :-)
WILCO!
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 about this issue.
> # https://rt
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 about this issue.
> # https://rt
# 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
=e
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: [perl #132353]
> # in the subject
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: [perl #132353]
> # in the subject
> 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 further special cases to the retu
> 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 further special cases to the retu
16 matches
Mail list logo
