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: 36540
Status: resolved
Priority: 0/
Queue: PPI

People
Owner: Nobody in particular
Requestors: user42 [...] zip.com.au
Cc:
AdminCc:

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



Subject: upper case letters in hexadecimal constants not parsed
Date: Sat, 07 Jun 2008 10:08:22 +1000
To: bug-PPI [...] rt.cpan.org
From: Kevin Ryde <user42 [...] zip.com.au>
Download (untitled) / with headers
text/plain 418b
Running "ppidump 0x10FF" (ppidump from perlcritic) gives PPI::Document PPI::Statement PPI::Token::Number::Hex '0x10' PPI::Token::Word 'FF' where I hoped the PPI::Token::Number::Hex would be '0x10FF'. There's similar dodginess with an upper case 'X', eg "ppidump 0Xff" PPI::Document PPI::Statement PPI::Token::Number '0' PPI::Token::Word 'Xff'
Subject: Re: [rt.cpan.org #36540] upper case letters in hexadecimal constants not parsed
Date: Sat, 05 Sep 2009 07:55:42 +1000
To: bug-PPI [...] rt.cpan.org
From: Kevin Ryde <user42 [...] zip.com.au>
I think this may be as easy as

Message body is not shown because sender requested not to inline it.

Message body is not shown because sender requested not to inline it.

I recommend using /[[:xdigit:]]/ instead of /[\da-f]/i
The full version of the fix for this is now released to CPAN as PPI 1.218.


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.