Skip Menu |

This queue is for tickets about the PPR CPAN distribution.

Report information
The Basics
Id: 122159
Status: resolved
Priority: 0/
Queue: PPR

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

Bug Information
Severity: (no value)
Broken in: 0.000005
Fixed in: (no value)



Subject: PPR rejects list of valid string literals
$ cat try.pl #!/usr/bin/env perl use strict; use warnings; use PPR; my $code = <<'_EOT_'; print <<X, qq! line 1 (in heredoc!) X line 3\n!; _EOT_ #print "Code: >>>\n$code<<<\n\n"; $code =~ m{\A (?&PerlDocument) \z $PPR::GRAMMAR }x or warn "Not valid Perl according to PPR"; eval $code; die $@ if $@; __END__ $ perl try.pl Not valid Perl according to PPR at try.pl line 16. line 1 (in heredoc!) line 3 $
Subject: Re: [rt.cpan.org #122159] PPR rejects list of valid string literals
Date: Mon, 26 Jun 2017 08:23:16 +1000
To: bug-PPR [...] rt.cpan.org
From: Damian Conway <damian [...] conway.org>
Thanks, Lukas. This problem is fixed in the next release. However, to fix it the module now requires that the $PPR::GRAMMAR variable must be interpolated at the beginning of the regex. I will look into removing that restriction, though I am not hopeful that I can. Damian