Skip Menu |

This queue is for tickets about the Perl-Critic-Pulp CPAN distribution.

Report information
The Basics
Id: 122064
Status: resolved
Priority: 0/
Queue: Perl-Critic-Pulp
People
Owner: Nobody in particular
Requestors: EDAVIS [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in: 92
Fixed in: (no value)

History Show all quoted text
  Sat Jun 10 08:39:18 2017 EDAVIS [...] cpan.org - Ticket created
Subject: ValuesAndExpressions::ProhibitUnknownBackslash and \N
I believe that ValuesAndExpressions::ProhibitUnknownBackslash needs to understand the \N named character escape sequence introduced in recent perls. E.g. $foo = "\N{CHECK MARK}";
  Sat Jun 17 02:32:41 2017 user42_kevin [...] yahoo.com.au - Correspondence added
Subject: Re: [rt.cpan.org #122064] ValuesAndExpressions::ProhibitUnknownBackslash and \N
Date: Sat, 17 Jun 2017 16:28:19 +1000
To: "EDAVIS via RT" <bug-Perl-Critic-Pulp [...] rt.cpan.org>
From: Kevin Ryde <user42_kevin [...] yahoo.com.au>
"EDAVIS via RT" <bug-Perl-Critic-Pulp@rt.cpan.org> writes: Show quoted text
> > I believe that ValuesAndExpressions::ProhibitUnknownBackslash needs to > understand the \N named character escape sequence introduced in recent > perls.
It understands, with "use charnames" (which extends back to 5.6 actually). I see it's brought in automatically by 5.16 up. I uploaded a version 94 which looks for "use 5.016" etc too. Thanks.
  Sat Jun 17 02:32:41 2017 The RT System itself - Status changed from 'new' to 'open'
  Thu May 14 03:18:01 2020 KRYDE [...] cpan.org - Status changed from 'open' to 'resolved'