Skip Menu |

This queue is for tickets about the Syntax-Feature-QwComments CPAN distribution.

Report information
The Basics
Id: 95229
Status: resolved
Priority: 0/
Queue: Syntax-Feature-QwComments

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: v1.12.0
Fixed in: (no value)



Subject: Test fails with perl 5.19.11
The fail reports will shortly be visible at http://matrix.cpantesters.org/?dist=Syntax-Feature-QwComments-v1.12.0 Regards, Slaven
Subject: Re: [rt.cpan.org #95229] Test fails with perl 5.19.11
Date: Thu, 1 May 2014 13:08:12 -0400
To: bug-Syntax-Feature-QwComments [...] rt.cpan.org
From: Eric Brine <ikegami [...] adaelis.com>
My first BBC, eh? I'll look into it this weekend if not sooner. Given the low-level nature of this module, it's probably something I need to fix on my end. On Thu, May 1, 2014 at 6:37 AM, Slaven_Rezic via RT < bug-Syntax-Feature-QwComments@rt.cpan.org> wrote: Show quoted text
> Thu May 01 06:37:17 2014: Request 95229 was acted upon. > Transaction: Ticket created by SREZIC > Queue: Syntax-Feature-QwComments > Subject: Test fails with perl 5.19.11 > Broken in: v1.12.0 > Severity: (no value) > Owner: Nobody > Requestors: SREZIC@cpan.org > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=95229 > > > > The fail reports will shortly be visible at > http://matrix.cpantesters.org/?dist=Syntax-Feature-QwComments-v1.12.0 > > Regards, > Slaven > >
Subject: Re: [rt.cpan.org #95229] Test fails with perl 5.19.11
Date: Thu, 1 May 2014 23:16:57 -0400
To: bug-Syntax-Feature-QwComments [...] rt.cpan.org
From: Eric Brine <ikegami [...] adaelis.com>
The module tries to mimic Perl's error messages, and they have changed. 5.18 and earlier: $ perl -e'qw' Can't find string terminator ";" anywhere before EOF at -e line 1. blead: $ ./perl -e'qw' Can't find string terminator ";" anywhere before EOF. I'm not sure if that change was intentional. Finding out...
Bisect points to [#perl 119593]
This problem was due to a bug introduced in perl itself. It has been fixed. This bug wasn't present in any stable release of perl, so no action needs to be taken.