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: 11682
Status: resolved
Worked: 10 min
Priority: 0/
Queue: PPI
People
Owner: adamk [...] cpan.org
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Important
Broken in: 0.902
Fixed in: (no value)

History Show all quoted text
  Mon Feb 28 05:04:59 2005 SREZIC [...] cpan.org - Ticket created
Subject: PPI::Tokenizer can't handle non-ASCII chars
PPI::Tokenizer can't handle perl sources which contain non-ASCII characters. I think the bit after line 373 in PPI/Tokenizer.pm (labelled with "Check for non-standard characters" may be removed --- perl can happily work with non-ASCII characters which are part of strings. Regards, Slaven
  Fri Mar 04 00:27:07 2005 adamk [...] cpan.org - Taken
  Thu Mar 10 23:23:54 2005 adamk [...] cpan.org - Correspondence added
Repeating since nobody but me apparently sees "comments" ------------- Support for non-"standard" (where standard has a specific definition in PPI) characters has been temporarily disabled to allow for more subtle bugs to be fixed without the "noise" of the extended char errors in the tinderbox process. Support for extended chars will be re-enabled, but will only be supported in "seeking" classes (strings, comments, POD) and not in normal code. Support for this needs to be added, so leaving this as a tracking bug.
  Wed Jun 08 04:53:06 2005 adamk [...] cpan.org - Status changed from 'new' to 'resolved'