Skip Menu |
 

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the PPI CPAN distribution.

Report information
The Basics
Id: 12880
Status: resolved
Worked: 5 min
Priority: 0/
Queue: PPI

People
Owner: Nobody in particular
Requestors: tokuhirom [...] yahoo.co.jp
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.903
Fixed in: (no value)



Subject: PPI::Tokenizer ALLOW_NONASCII problem
Download (untitled) / with headers
text/plain 780b
I found a bug in PPI::Tokenizer. I think, this logic is inverse. In current version, always reject the NONASCII. --- Tokenizer.pm.org 2005-05-19 22:38:40.000000000 +0900 +++ Tokenizer.pm 2005-05-19 23:03:51.000000000 +0900 @@ -161,7 +161,7 @@ } # Check for non-standard characters - if ($ALLOW_NONASCII or $self->{source} =~ /([^abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789;\[\]{}()=?|+<>.!~^*\$\@&:\%#,'"`\\\/_ \n\t-])/ ) { + if ( ! $ALLOW_NONASCII and $self->{source} =~ /([^abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789;\[\]{}()=?|+<>.!~^*\$\@&:\%#,'"`\\\/_ \n\t-])/ ) { return $self->_error( "Source code contains unsupported characters (first one encountered was '$1')" ); }


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.