Mon Dec 27 17:18:29 UTC 2010 - pascal.bleser@opensuse.org
- update to 0.015:
* added support for Perl 5.13.6 (?^...) construction
* added support for Perl 5.13.6 d, l, and u modifiers
* fixed inconsistency in perl_version_introduced() results between PPIx::Regexp::Token::Modifier and PPIx::Regexp::Token::GroupType::Modifier
- changes from 0.014:
* recognize \o{...} as a PPIx::Regexp::Token::Literal, with perl_version_introduced() of 5.0013003
* terminate \0.. through \7.. after three characters, as Perl does
* correct the PPIx::Regexp::Token::Literal ordinal() method for '\b' -- as a literal, this is a back space
- changes from 0.013:
* declare a parse failure if characters are found between the '}' and the ')' of (?{...}) and (??{...}), and rebless the tokens to ::Unknown: Perl does not accept anything here, so I think I should not either
* whitespace tweak in the PPIx::Regexp::Dumper test output for the failures test
* replace the PPI logic in PPIx::Regexp::Token::Code with a call to $tokenizer->find_matching_delimiter(): this is actually the way Perl works, as a look at toke.c and regcomp.c makes clear
* push the perl_version_introduced() back to 5.0
- changes from 0.012:
* track all the features reported as introduced (or removed) in Perl 5.010 back to Perl 5.009005, and report them as such
* report modifier /r as having been introduced in Perl 5.013002, rather than the default of 5.006
- changes from 0.010_01:
* remove dependencies on Params::Util and Readonly
* parse POSIX character classes [=a=] and [.a.] as PPIx::Regexp::Token::CharClass::POSIX::Unknown, which counts as a parse failure since these are not supported by Perl
- changes from 0.010: fix fatal error in PPIx::Regexp::Token::Code->ppi()
- changes from 0.009: recognize s/.../.../ee as being different from s/.../.../e. In particular, the replacement portion of the former is _not_ a Perl expression: it's an interpolatble string, which later gets eval{}'ed
