| 1 |
0.092 2026-06-13 T. R. Wyant |
| 2 |
Remove references to the RT bug tracking system. |
| 3 |
|
| 4 |
Replace [email protected] with [email protected]. |
| 5 |
|
| 6 |
Correct documentation errors. |
| 7 |
|
| 8 |
No functional changes. |
| 9 |
|
| 10 |
0.091 2025-10-06 T. R. Wyant |
| 11 |
Code review on use of 'PPI::Document'. I concluded it was not needed |
| 12 |
in PPIx::Regexp::Token::Interpolation and |
| 13 |
PPIx::Regexp::Token::Literal, but that it needed to be added to |
| 14 |
PPIx::Regexp::Tokenizer. The purpose of this release is to submit |
| 15 |
the changes to the tender mercies of the CPAN testers. |
| 16 |
|
| 17 |
0.090_01 2025-09-27 T. R. Wyant |
| 18 |
Avoid "Possible attempt to escape whitespace" warning, which is |
| 19 |
emitted in perl-5.43.2 and forward. Thanks to James E. Keenan for |
| 20 |
the pull request. |
| 21 |
|
| 22 |
0.090 2025-09-21 T. R. Wyant |
| 23 |
Explain s///eee... Perl commit 040a4d7 (perlop: properly document |
| 24 |
s///e modifier) by mauke, makes perlop explicitly state that more |
| 25 |
than 2 'e' modifiers are permitted, and cause the result of the |
| 26 |
expression to be eval-ed n-1 times, where n is the number of 'e' |
| 27 |
modifiers. |
| 28 |
|
| 29 |
Fix typo in comment. Thanks to Michal Josef Špaček for picking this |
| 30 |
up and providing the pull request. |
| 31 |
|
| 32 |
0.089 2025-05-18 T. R. Wyant |
| 33 |
The /x modifier should not affect the parse of the replacement |
| 34 |
string in a substitution operator. That is, the '#' in s/x/#/x does |
| 35 |
NOT introdice a comment. |
| 36 |
|
| 37 |
Correct POD link in PPIx::Regexp::Token::Literal. |
| 38 |
|
| 39 |
Annotate sub class(), since with Perl 5.38 it is a built-in. |
| 40 |
|
| 41 |
0.088 2023-02-28 T. R. Wyant |
| 42 |
Remove support for (**{ ... code ... }). This was introduced in |
| 43 |
Perl 5.37.8 along with a single-splat version. The double-splat |
| 44 |
version was removed without deprecation in Perl 5.37.9, so it is |
| 45 |
being removed without deprecation here as well, per my stated policy |
| 46 |
about development functionality. The single-splat version still |
| 47 |
exists (and is documented) in Perl 5.37.9, and in this package. |
| 48 |
|
| 49 |
0.087 2023-01-28 T. R. Wyant |
| 50 |
Add support for code in optimized regex, a.k.a. (*{...}). This |
| 51 |
involved making the recognition of backtracking control more |
| 52 |
specific, since it also uses (?*...). |
| 53 |
|
| 54 |
If (*{...}) and (**{...}) are removed from Perl before Perl 5.38.0, |
| 55 |
support for them will be removed from this package. |
| 56 |
|
| 57 |
0.086 2022-12-13 T. R. Wyant |
| 58 |
Add width(), which returns the number of characters matched. Note |
| 59 |
that an indefinite upper boumd is represented as IEEE 754 Inf if |
| 60 |
that appears to be supported; otherwise by a singleton object |
| 61 |
overloaded to allow stringification, numification, and numeric |
| 62 |
tests. |
| 63 |
|
| 64 |
Use width() to enhance the detection of variable-width look-behinds. |
| 65 |
|
| 66 |
Serious clean-up on accepts_perl() subsystem. |
| 67 |
|
| 68 |
0.085 2022-04-16 T. R. Wyant |
| 69 |
Remove 'postderef' argument to PPIx::Regexp->new(). Postfix |
| 70 |
dereference is always recognized. |
| 71 |
|
| 72 |
0.084 2022-04-02 T. R. Wyant |
| 73 |
Require PPI 1.238 for postfix deref support, and recode the |
| 74 |
postfix deref logic in terms of 1.238's functionality. |
| 75 |
|
| 76 |
Parse '@{[ ... ]}' as code, not interpolation. This is more in line |
| 77 |
with what it actually represents, and allows correct versioning of |
| 78 |
postfix dereferences. But is is an incompatible change. |
| 79 |
|
| 80 |
0.083 2022-03-17 T. R. Wyant |
| 81 |
Correct and optimize the computation of logical column position (the |
| 82 |
one that takes account of tabs). |
| 83 |
|
| 84 |
0.082 2021-11-29 T. R. Wyant |
| 85 |
Add --version to eg/predump, and document all options with double |
| 86 |
dashes. |
| 87 |
|
| 88 |
Silence 'uninitialized' warning generated by /(?<=.{35})/. |
| 89 |
Thanks to Brian Fraser for reporting this. |
| 90 |
|
| 91 |
Try to quell weird Win32 test failures which seem to occur only in |
| 92 |
tests where I am using 'use open' to put the standard handles into |
| 93 |
UTF-8 mode. The fix (I hope) is to do this to the Test::Harness |
| 94 |
handles at run time instead of to the standard handles at compile |
| 95 |
time. |
| 96 |
|
| 97 |
Add file CONTRIBUTING. |
| 98 |
|
| 99 |
0.081 2021-10-22 T. R. Wyant |
| 100 |
Any use of the postderef argument is now fatal. |
| 101 |
|
| 102 |
Correct generation of 'provides' metadata. Thanks to Favio Poletti |
| 103 |
for blogging |
| 104 |
https://github.polettix.it/ETOOBUSY/2021/06/15/the-real-pause-workaround/, |
| 105 |
and ultimately to Joel Berger for the pointer to |
| 106 |
https://metacpan.org/pod/CPAN::Meta::Spec#no_index |
| 107 |
|
| 108 |
Add YAPE::Regex to SEE ALSO |
| 109 |
|
| 110 |
0.080 2021-04-16 T. R. Wyant |
| 111 |
All uses of the postderef argument to new() now warn. |
| 112 |
|
| 113 |
0.079 2021-03-26 T. R. Wyant |
| 114 |
Get prerequisites up to snuff, and add xt/author/prereq.t to ensure |
| 115 |
they stay that way. |
| 116 |
|
| 117 |
Add rt.cpan.org back to bug reporting methods. Long live RT! |
| 118 |
|
| 119 |
0.078 2021-01-28 T. R. Wyant |
| 120 |
Allow CPAN to index Script_Run, Atomic_Script_Run, since they made |
| 121 |
it into a production release. |
| 122 |
|
| 123 |
Allow {,3} and { 0 , 3 } as quantifiers, requiring at least Perl |
| 124 |
5.33.6. Previously these parsed as literals. This parse will be |
| 125 |
retracted if it does not make it into 5.34.0. |
| 126 |
|
| 127 |
0.077 2021-01-14 T. R. Wyant |
| 128 |
Add Travis CI testing. |
| 129 |
|
| 130 |
Use GitHub as bug tracker. R.I.P. rt.cpan.org. |
| 131 |
|
| 132 |
0.076 2020-11-28 T. R. Wyant |
| 133 |
Correct (I hope) detection of \K in nested assertions. |
| 134 |
|
| 135 |
Variable-length look-behind is version 5.029009. |
| 136 |
|
| 137 |
Look-behinds quantified longer than 255 characters are an error, and |
| 138 |
are made into unknown tokens or structures. I ended up refactoring |
| 139 |
the PPIx::Regexp::Token::GroupType class initialization for the |
| 140 |
latter two changes. |
| 141 |
|
| 142 |
0.075 2020-10-08 T. R. Wyant |
| 143 |
Warn on first use of attribute 'postderef'. |
| 144 |
|
| 145 |
0.074 2020-09-08 T. R. Wyant |
| 146 |
Remove PPIx::Regexp::StringTokenizer itself and all documentation |
| 147 |
referring to it or the 'parse' argument to PPIx::Regexp->new(). |
| 148 |
|
| 149 |
0.073 2020-07-28 T. R. Wyant |
| 150 |
Remove prototypes from testing subroutines defined in t/*.t. |
| 151 |
|
| 152 |
0.072 2020-05-20 T. R. Wyant |
| 153 |
Drop dependency on List::MoreUtils. Thanks to Graham Ollis |
| 154 |
(plicease) for bringing the issues with this module to my attention. |
| 155 |
|
| 156 |
0.071 2020-03-28 T. R. Wyant |
| 157 |
Recognize wildcard Unicode names (Perl 5.31.10). |
| 158 |
|
| 159 |
Try to get correct line number in derived PPI. This is done by |
| 160 |
injecting "\n" as needed. The initial #line directive becomes "#line |
| 161 |
2", but is suppressed if I need to generate line 1. |
| 162 |
|
| 163 |
Improve normalization of content for ppi(). This involves the |
| 164 |
un-bracketing of things like ${foo}. |
| 165 |
|
| 166 |
Deprecate new() argument postderef. At this stage it is only |
| 167 |
documented as deprecated. In the first release after October 1 2020 |
| 168 |
it will warn on the first use. Eventually it will be retracted, and |
| 169 |
postfix dereferences will always be recognized. This is the default |
| 170 |
behavior now. |
| 171 |
|
| 172 |
Add dump argument/option 'short' which, if true, causes leading |
| 173 |
'PPIx::Regexp::' to be removed from class names. |
| 174 |
|
| 175 |
0.070 2020-02-27 T. R. Wyant |
| 176 |
Add index_locations option to PPIx::Regexp->new(). This defaults to |
| 177 |
true if the regexp is specified as a PPI::Element object. The |
| 178 |
locations are consistent with the containing PPI::Document. |
| 179 |
|
| 180 |
Add methods location(), column_number(), line_number(), |
| 181 |
logical_filename(), logical_line_number(), and |
| 182 |
visual_column_number() to PPIx::Regexp::Element. All return undef if |
| 183 |
the locations could not be determined. |
| 184 |
|
| 185 |
Add method statement() to PPIx::Regexp::Element. This returns the |
| 186 |
PPI statement containing the regexp element, or nothing if none. |
| 187 |
|
| 188 |
Add method is_matcher() to PPIx::Regexp::Element. This classifies |
| 189 |
objects as to whether they actually match something in the target |
| 190 |
string. Possible returns are true (they do), false but defined (they |
| 191 |
do not) and undef (no clue). |
| 192 |
|
| 193 |
Add methods first_token() and last_token() to PPIx::Regexp::Node. |
| 194 |
|
| 195 |
Add methods next_token() and previous_token() to |
| 196 |
PPIx::Regexp::Element. |
| 197 |
|
| 198 |
0.069 2020-02-07 T. R. Wyant |
| 199 |
The PPIx::Regexp->new() 'parse' option is now fatal. This selected |
| 200 |
either string or regex parse. I consider the string parse a failed |
| 201 |
experiment. This is the latest step in removing it in favor of the |
| 202 |
PPIx::QuoteLike package. |
| 203 |
|
| 204 |
0.068 2020-01-21 T. R. Wyant |
| 205 |
Expose PPIx::Regexp::Util::is_ppi_regexp_element() |
| 206 |
|
| 207 |
explain() on [[=x=]] now calls it a Character Equivalence. |
| 208 |
It's still a PPIx::Regexp::Token::CharClass::POSIX::Unknown (and |
| 209 |
therefore an error), though. |
| 210 |
|
| 211 |
0.067 2019-08-30 T. R. Wyant |
| 212 |
\K was retracted in Perl 5.31.3, but only inside look-around |
| 213 |
assertions. |
| 214 |
|
| 215 |
0.066 2019-08-16 T. R. Wyant |
| 216 |
Fix broken POD, and add tests to ensure it remains fixed. |
| 217 |
|
| 218 |
0.065 2019-05-25 T. R. Wyant |
| 219 |
Quash undef error in __is_ppi_regexp_element() when passed a |
| 220 |
PPI::Token::Regexp::Transliterate |
| 221 |
|
| 222 |
Support proper version for qr'\N{name}'. Until 5.29.10 this |
| 223 |
construction failed to parse because it did not interpolate. But |
| 224 |
PPIx::Regexp blithely ignored this detail. As of 5.29.10, something |
| 225 |
like m'\N{LATIN CAPITAL LETTER L}' matches identically to m'L'. So I |
| 226 |
implemented introduction as of that version. |
| 227 |
|
| 228 |
Have explain() recognize Unicode property wildcards. |
| 229 |
|
| 230 |
0.064 2019-04-01 T. R. Wyant |
| 231 |
Empty \p{} should be an error. |
| 232 |
|
| 233 |
\x{} and \x{ non-hex } should be errors under "use re 'strict'" |
| 234 |
|
| 235 |
\o{} should be an error |
| 236 |
|
| 237 |
\o{ non-octal } should be an error under "use re 'strict'" |
| 238 |
|
| 239 |
Support wildcard Unicode property values. These were added in |
| 240 |
5.29.9. |
| 241 |
|
| 242 |
Add eg/find-variable-length-lookarounds |
| 243 |
|
| 244 |
Add convenience method extract_regexps(). This is a static method |
| 245 |
on PPIx::Regexp that takes as its argument a PPI::Document and |
| 246 |
manufactures PPIx::Regexp objects out of anything that parses to a |
| 247 |
regexp of some sort. |
| 248 |
|
| 249 |
Don't run illegal character tests before Perl 5.18 unless we're |
| 250 |
author testing, because they are noisy. I think the issue is not the |
| 251 |
Perl version per se, but the version of Unicode; Perl5180delta says |
| 252 |
it shipped with Unicode 6.2. |
| 253 |
|
| 254 |
0.063 2018-11-08 T. R. Wyant |
| 255 |
Silence weird-character parse tests and make them no longer |
| 256 |
author-only. |
| 257 |
|
| 258 |
Further deprecate 'parse' argument to new(). You now get a warning |
| 259 |
on each use. |
| 260 |
|
| 261 |
0.062 2018-08-12 T. R. Wyant |
| 262 |
Remove tokenizer method prior(). This is the last step in its |
| 263 |
deprecation. |
| 264 |
|
| 265 |
0.061 2018-07-09 T. R. Wyant |
| 266 |
Only standalone graphemes and non-characters allowed as delimiters |
| 267 |
starting with Perl 5.29.0. |
| 268 |
|
| 269 |
Non-ASCII delimiters started working in 5.8.3, so that is what |
| 270 |
perl_version_introduced() returns for them. |
| 271 |
|
| 272 |
Collateral with all this, accept word characters as delimiters, but |
| 273 |
only with at least one space between the operator and the expression |
| 274 |
-- that is, 'qr xyx' is OK, but 'qrxyx' is not. |
| 275 |
|
| 276 |
0.060 2018-06-16 T. R. Wyant |
| 277 |
\N{} now parses as the unknown token, not NoOp, regardless of the |
| 278 |
setting of 'use re qw< strict >;'. \N{} became unconditionally fatal |
| 279 |
in 5.28.0 (5.27.1, actually). The policy when the parse changes is |
| 280 |
to use the most-modern parse. Hence this change. |
| 281 |
|
| 282 |
As a side effect of this, the unknown token's explain() method now |
| 283 |
returns something -- normally the associated error. |
| 284 |
|
| 285 |
Add method remove_insignificant(). If the invocant isa Node, this |
| 286 |
returns a clone of the invocant with non-significant elements |
| 287 |
removed. Otherwise it returns either the invocant or nothing. |
| 288 |
|
| 289 |
0.059 2018-05-08 T. R. Wyant |
| 290 |
Install @CARP_NOT everywhere so that warnings and exceptions |
| 291 |
generated in the bowels of the system appear to come from the point |
| 292 |
where the system is entered. |
| 293 |
|
| 294 |
Further deprecate string (versus regexp) parsing. The first use of |
| 295 |
the 'parse' argument to new() will result in a warning. If the |
| 296 |
value of the argument is 'guess' or 'string', the warning refers to |
| 297 |
PPIx::QuoteLike. |
| 298 |
|
| 299 |
0.058 2018-04-26 T. R. Wyant |
| 300 |
Prefer /[0-9]/ over /\d/ for numeric checks. The latter can match |
| 301 |
non-ASCII digits. |
| 302 |
|
| 303 |
Explain the negated POSIX character classes. Also tweak some of the |
| 304 |
asserted explanations -- mostly for readability and parallel |
| 305 |
construction with the negated explanations, but it turns out |
| 306 |
[[:digit:]] is NOT equivalent to [0-9]. |
| 307 |
|
| 308 |
0.057 2018-04-17 T. R. Wyant |
| 309 |
Allow ->asserts( 'a*' ). This modification actually allows wild |
| 310 |
cards in asserts() on all match semantic modifiers, but it is |
| 311 |
probably only useful in the case of 'a*', because that is the only |
| 312 |
one that can be doubled. |
| 313 |
|
| 314 |
Explain grouping structure as 'Grouping', not 'Capture or grouping'. |
| 315 |
|
| 316 |
Caret modifier was not turning off /n. This was complicated by the |
| 317 |
fact that (?^) was introduced in 5.13.6, but (?n) was not introduced |
| 318 |
until 5.21.8. The solution was to include -n in the expansion of the |
| 319 |
caret if and only if /n had been seen in the scope of the caret. |
| 320 |
|
| 321 |
Recognize caret in /(?^)x/. |
| 322 |
|
| 323 |
Acknowledge Regexp::Parsertron in SEE ALSO |
| 324 |
|
| 325 |
0.056 2018-03-07 T. R. Wyant |
| 326 |
Support removal of unescaped literal left curlys after left parens, |
| 327 |
which was deprecated in 5.27.8. No actual change in output yet, |
| 328 |
since deprecation is not tracked, but the perl_version_removed() |
| 329 |
logic is there. |
| 330 |
|
| 331 |
|
| 332 |
Add next_element() and kin. These are analogous to next_sibling() |
| 333 |
and kin, but will cross over from content proper into structure |
| 334 |
(beginning and end delimiters, etc) and vice versa. |
| 335 |
|
| 336 |
Correct requirements_for_perl() for impossible regular expression. |
| 337 |
It now returns '! $]' when the components of the regexp are valid, but |
| 338 |
none are valid under any specific version of Perl. It used to think all |
| 339 |
Perls were OK when this happened. |
| 340 |
|
| 341 |
Add the alpha_assertions introduced in 5.27.9. |
| 342 |
|
| 343 |
Handle 5.27.9's change from +script_run to *script_run, and support |
| 344 |
*sr as a synonym. |
| 345 |
|
| 346 |
0.055 2018-02-08 T. R. Wyant |
| 347 |
Tokenizer method prior() is now fatal. This was documented as |
| 348 |
package-private, but as it WAS documented, I am putting it through a |
| 349 |
deprecation cycle anyway. Six months from now it will be removed. |
| 350 |
|
| 351 |
Add Script_Run classes as subclasses to their superclass docs. This |
| 352 |
was missed in the last update. |
| 353 |
|
| 354 |
0.054 2018-01-29 T. R. Wyant |
| 355 |
Add support for (+script_run:...). This is an experimental feature |
| 356 |
added in Perl 5.27.8. It imposes on any matches it contains the |
| 357 |
additional restriction that everything matched has to belong to the |
| 358 |
same Unicode script. This support will be retracted if the |
| 359 |
functionality does not make it into Perl 5.28. |
| 360 |
|
| 361 |
Add method scontent(). This returns significant content only. That |
| 362 |
is, if called on the parse of '/ f u b a r /x', it returns |
| 363 |
'/fubar/x'. |
| 364 |
|
| 365 |
0.053 2017-10-30 T. R. Wyant |
| 366 |
Recognize \px as Unicode char class. At least, when the x is C, L, |
| 367 |
M, N, P, S or Z. |
| 368 |
|
| 369 |
The 'parse' argument to new() is now deprecated. |
| 370 |
|
| 371 |
0.052 2017-09-07 T. R. Wyant |
| 372 |
RT 122715: Clarify Node->find_parents() documentation. Thanks to |
| 373 |
Salvatore Bonaccorso for letting me know about this problem. |
| 374 |
|
| 375 |
Further deprecate tokenizer method prior() in favor of |
| 376 |
prior_significant_token(). |
| 377 |
|
| 378 |
|
| 379 |
Add requirements_for_perl(). This is analogous to the |
| 380 |
CPAN::Meta::Requirements method requirements_for_module(), though |
| 381 |
the output is formatted differently. Also put in the actual |
| 382 |
requirements for an un-escaped literal left curly after a constant, |
| 383 |
which was removed in 5.25.1 and reinstated in 5.27.1. |
| 384 |
|
| 385 |
Add accepts_perl(). This is analogous to |
| 386 |
CPAN::Meta::Requirements->accepts_module(). I decided that |
| 387 |
CPAN::Meta;:Requirements was overkill, but this may turn out to be |
| 388 |
the wrong decision, so I will be careful what I expose. |
| 389 |
|
| 390 |
Document behavior of perl_version_introduced() and |
| 391 |
perl_version_removed() when a feature is re-introduced after |
| 392 |
removal, or re-removed after re-introduction. |
| 393 |
|
| 394 |
\N{} (empty curlys) removed in 5.27.1. |
| 395 |
|
| 396 |
0.051 2017-01-29 T. R. Wyant |
| 397 |
Support whitespace inside [] if /xx in effect. |
| 398 |
Starting with Perl 5.25.9, a space or tab appearing inside a bracketed |
| 399 |
character class is not significant if /xx is asserted. |
| 400 |
|
| 401 |
Further deprecate tokenizer method prior() |
| 402 |
|
| 403 |
Add 'provides' data to ExtUtils::MakeMaker output |
| 404 |
|
| 405 |
SOME unescaped litaral '{' removed in 5.025001. |
| 406 |
After '.', Unicode classes, and bracketed classes (including extended) |
| 407 |
they are still legal. |
| 408 |
|
| 409 |
Make /\b{/ an error |
| 410 |
Perl fails to parse the above, because once it sees the '\b{' it wants |
| 411 |
to find one of the extended boundary assertions (like \b{wb}), and |
| 412 |
declares an error when it does not. So we check for this and rebless the |
| 413 |
curly into an unknown token, not a literal. |
| 414 |
|
| 415 |
0.050 2016-05-06 T. R. Wyant |
| 416 |
Parse bracketed substitution with embedded comment. This is something |
| 417 |
like s{foo}\n#{bar}\n{baz} which is equivalent to s/foo/baz/. PPI |
| 418 |
gets this wrong, and we're not smart enough to fix up the PPI parse, |
| 419 |
but if given this as text, we now parse it correctly. |
| 420 |
|
| 421 |
We now recognize postfix dereferences by default, since Perl does |
| 422 |
beginning with 5.24. In other words, default new() argument |
| 423 |
'postderef' to true. |
| 424 |
|
| 425 |
Unterminated substitutions (i.e. 's//') should no longer cause an |
| 426 |
exception. Instead they parse as an unknown token. |
| 427 |
|
| 428 |
0.049 2016-04-19 T. R. Wyant |
| 429 |
Robustify PPIx::Regexp->perl_version_removed() |
| 430 |
The problem here was that if the expression being parsed was |
| 431 |
sufficiently badly-formed, $self->delimiters() would be undef, throwing |
| 432 |
a warning. |
| 433 |
|
| 434 |
Correct dump of embedded modifiers (eg: (?i:...)) |
| 435 |
|
| 436 |
0.048 2016-02-29 T. R. Wyant |
| 437 |
Add option 'strict', like 'use re "strict"' |
| 438 |
In the presence of strict(), I opted to set perl_version_introduced |
| 439 |
to the version of Perl where the construct became an error. |
| 440 |
|
| 441 |
Parse '\N{}' as no-op. |
| 442 |
The previous parse was a character class ('\N') followed by two |
| 443 |
literals ('{' and '}'). But perl5238delta said that it had been |
| 444 |
ignored up to that time. Starting with 5.23.8 it is an error if 'use |
| 445 |
re strict' is in effect. |
| 446 |
|
| 447 |
Quash 'NOT a POSIX class ...' warning under 5.23.8 |
| 448 |
|
| 449 |
Add Makefile targets authortest and testcover. |
| 450 |
|
| 451 |
0.047 2016-01-29 T. R. Wyant |
| 452 |
Recognize \b{lb}, introduced in 5.23.7. If this is retracted before |
| 453 |
5.24, it will be removed outright. |
| 454 |
|
| 455 |
0.046 2016-01-08 T. R. Wyant |
| 456 |
Add GitHub repository to mmetadata. |
| 457 |
|
| 458 |
0.045 2015-12-31 T. R. Wyant |
| 459 |
Deprecate tokenizer method prior() in favor of |
| 460 |
prior_significant_token(). This is not part of the public interface, |
| 461 |
so I suppose I could have just slam-dunked it, but ... |
| 462 |
|
| 463 |
Add ability to parse strings as well as regexes |
| 464 |
The new functionality is controlled by the new new() argument |
| 465 |
'parse', whose permitted values are 'regex' (the default), 'string', |
| 466 |
or 'guess'. String parsing, and the 'string' and 'guess' values of |
| 467 |
'parse', are experimental. |
| 468 |
|
| 469 |
0.044 2015-12-08 T. R. Wyant |
| 470 |
Allow nesting of \Q with \U, \L, and \F |
| 471 |
The perlop docs say these nest with each other. Playing with Perl |
| 472 |
suggests that \U, \L and \F supersede each other, but thet they as a |
| 473 |
group nest with \Q in either order, so that if you specify \Q and |
| 474 |
one of the \U, \L, \F group you need two \Es to turn them all back |
| 475 |
off. |
| 476 |
|
| 477 |
Restrict recognition of back references in replacement strings to |
| 478 |
\number form, since Perl itself does not recognize \g{...} or |
| 479 |
\k{...} there. |
| 480 |
|
| 481 |
Recognize postfix dereference if desired. This is controlled by the |
| 482 |
Boolean argument 'postderef' passed to PPIx::Regexp->new(). The |
| 483 |
default is false, but will become true if postfix dereference |
| 484 |
becomes mainstream Perl 5. |
| 485 |
|
| 486 |
Add explain() and supporting methods main_structure() and |
| 487 |
in_regex_set(). The explain() method returns a brief explanation of |
| 488 |
what the element does. |
| 489 |
|
| 490 |
0.043 2015-11-18 T. R. Wyant |
| 491 |
Do not end regex set prematurely on finding '])' |
| 492 |
The problem is that '])' can occur within an extended bracketed |
| 493 |
character class if it contains grouping parentheses and the last |
| 494 |
item in a group is a regular bracketed character class and there is |
| 495 |
no white space between the end of the character class and the end of |
| 496 |
the group. |
| 497 |
|
| 498 |
Record parse failure if switch condition is unknown |
| 499 |
The structure was being reblessed to |
| 500 |
PPIx::Regexp::Structure::Unknown, but the number of parse failures |
| 501 |
was not being incremented. |
| 502 |
|
| 503 |
Parse \U and friends as meta-characters inside \Q...\E |
| 504 |
This turns out to be what Perl itself does, as shown by |
| 505 |
$ perl -E 'say qr{\Q\Ufoo}' |
| 506 |
|
| 507 |
Clear error when lexer identifies unknown token. Those who peruse the |
| 508 |
changes in this release will see that a bunch of refactoring was |
| 509 |
done as part of this. |
| 510 |
|
| 511 |
Parse white space inside bracketed character classes inside extended |
| 512 |
bracketed character classes (whew!) as literals, except for the |
| 513 |
space character itself and the horizontal tab. This tracks the |
| 514 |
corresponding change in Perl 5.23.4. This will be reverted if the |
| 515 |
corresponding Perl change does not make it into 5.24.0. |
| 516 |
|
| 517 |
Beginning with version 0.035, PPIx::Regexp was incorrectly reporting |
| 518 |
the sense of modifiers when the same token both asserted and negated |
| 519 |
modifiers (e.g. '(?x-i:...)'). This release should correct the |
| 520 |
problem. |
| 521 |
|
| 522 |
Document policy when Perl changes in such a way that the proper parse |
| 523 |
for a regular expression changes. In this case the more modern parse |
| 524 |
is preferred. |
| 525 |
|
| 526 |
0.042 2015-10-09 T. R. Wyant |
| 527 |
Report error rather than failing when parsing a string consisting |
| 528 |
wholly of white space. |
| 529 |
|
| 530 |
Group types were not being recognized if they contained the delimiter |
| 531 |
character for the regexp (e.g. in qr<(?\<foo)> the look-behind |
| 532 |
assertion was not recognized as such). |
| 533 |
|
| 534 |
Correct mis-parse of ' s///'. Leading white space is supposed to be |
| 535 |
acceptable, but the leading whitespace token caused |
| 536 |
PPIx::Regexp::Lexer not to recognize the substitution as such. |
| 537 |
|
| 538 |
Tokenizer was failing when the string to be parsed was so bad it was |
| 539 |
trying to return the whole thing as a single |
| 540 |
PPIx::Regexp::Token::Unknown. |
| 541 |
|
| 542 |
PPIx::Regexp::Dumper now displays a message if a structure is missing |
| 543 |
its end delimiter. |
| 544 |
|
| 545 |
RT 107331 Produce parse error in the presence of trailing cruft. |
| 546 |
Thanks to Klaus Rindfrey for catching this. |
| 547 |
The tokenizer now does a preliminary scan for delimiting brackets |
| 548 |
and modifiers. Anything after the modifiers except for white space |
| 549 |
is now made into a PPIx::Regexp::Token::Unknown, resulting in a |
| 550 |
parse failure being reported. The previous implementation simply |
| 551 |
assumed a valid expression, and in the case of the expression in the |
| 552 |
ticket blithely mismatched the delimiters and returned a parse |
| 553 |
without failures, but which was manifestly bogus. |
| 554 |
|
| 555 |
Tweak documentation in PPIx::Regexp. |
| 556 |
|
| 557 |
0.041 2015-07-02 T. R. Wyant |
| 558 |
Report \C (match octet) as removed in 5.23.0. |
| 559 |
|
| 560 |
Accept non-ASCII whitespace under /x. The Whitespace object can be |
| 561 |
multiple characters; the perl_version_introduced() becomes |
| 562 |
'5.021001' if any of them is a code point above 127. |
| 563 |
|
| 564 |
The perl_version_removed() method now returns '5.021001' when called |
| 565 |
on a PPIx::Regexp object produced by parsing '?foo?' (match once |
| 566 |
without explicit 'm'). The object produced by parsing 'm?foo?' still |
| 567 |
returns the minimum Perl version. |
| 568 |
|
| 569 |
0.040 2015-05-31 T. R. Wyant |
| 570 |
Do not parse unadorned parentheses as capture groups when /n is in |
| 571 |
effect. Instead, they are parsed as PPIx::Regexp::Structure. Named |
| 572 |
captures appear to be unaffected by /n. |
| 573 |
|
| 574 |
Made a verbose dump a little more so. Specifically, dump |
| 575 |
max_capture_group where relevant, and display dumped values a bit |
| 576 |
more informatively. |
| 577 |
|
| 578 |
Report /n (no captures) as having been added in 5.21.8. |
| 579 |
|
| 580 |
0.039 2015-04-02 T. R. Wyant |
| 581 |
Recognize nested subscripts in interpolation. |
| 582 |
Thanks to Andy Lester for finding this, which actually manifested in |
| 583 |
Perl-Critic-Policy-Variables-ProhibitUnusedVarsStricter. The problem is |
| 584 |
that the actual heuristics for finding the end of an interpolation are |
| 585 |
undocumented, and I missed this rather-obvious case. |
| 586 |
|
| 587 |
Add \b{g} (= \b{gcb}) |
| 588 |
|
| 589 |
0.038 2015-03-09 T. R. Wyant |
| 590 |
Make \b{foo} into an unknown token (and therefore an error. This |
| 591 |
applies to \b{anything}, where 'anything' is anything bur 'gcb', |
| 592 |
'wb', or 'sb'. |
| 593 |
|
| 594 |
Handle the boundary assertions introduced in Perl 5.21.9: '\b{gcb}' |
| 595 |
(grapheme cluster boundary), '\b{wb}' (word boundary), '\b{sb}' |
| 596 |
(sentence boundary), and the corresponding '\B{...}' constructions. |
| 597 |
Similar-looking things like '\b{foo}' are not recognized as |
| 598 |
assertions, and end up being literals. This is less general than I |
| 599 |
usually make things, but was done against the possibility that |
| 600 |
(e.g.) '\b{foo}' might be introduced later, requiring |
| 601 |
perl_version_released() to return a different number. Any of these |
| 602 |
retracted prior to Perl 5.22.0 will simply be removed from |
| 603 |
PPIx::Regexp. |
| 604 |
|
| 605 |
0.037 2014-11-12 T. R. Wyant |
| 606 |
Have PPIx::Regexp::Structure::RegexSet POD recognize that the Perl |
| 607 |
docs (specifically perlrecharclass) now call this construction |
| 608 |
Extended Bracketed Character Classes, not sets. |
| 609 |
|
| 610 |
Correctly mark the replacement portion of s///ee as code. Prior to |
| 611 |
this release it was parsed as though no /e were present. |
| 612 |
|
| 613 |
Make available the number of times a given modifier is asserted |
| 614 |
(except for the match semantics modifiers which get handled |
| 615 |
differently). See PPIx::Regexp::Token::Modifier->asserted() and |
| 616 |
PPIx::Regexp::Tokenizer->modifier() for details. |
| 617 |
|
| 618 |
0.036 2014-01-04 T. R. Wyant |
| 619 |
Retract the "Allow non-ASCII white space under /x" change introduced |
| 620 |
in version 0.033. I misread perl5170delta, and implemented early. |
| 621 |
|
| 622 |
Change to explicit character class to recognize white space under /x. |
| 623 |
I was previously using \s, which matched too much. Thanks to Nobuo |
| 624 |
Kumagai for finding and reporting this. |
| 625 |
|
| 626 |
0.035 2013-11-15 T. R. Wyant |
| 627 |
Properly handle multi-character modifiers like /ee. We now handle /eie |
| 628 |
as being the same as /eei. Thanks to Anonymous Monk for finding |
| 629 |
this. |
| 630 |
|
| 631 |
Properly handle \g and \k back references that do not correspond to an |
| 632 |
actual capture group. They are now reblessed into the unknown token, |
| 633 |
and counted as errors. Thanks to Anonymous Monk for finding this. |
| 634 |
|
| 635 |
Add method error() to PPIx::Regexp::Element. This should return an |
| 636 |
error message when the element is in error -- normally when it has |
| 637 |
been blessed into the unknown token or structure. |
| 638 |
|
| 639 |
Add method modifier_asserted() to PPIx::Regexp::Element. This walks |
| 640 |
the parse tree backward to determine if the given modifier is in |
| 641 |
effect for the element. |
| 642 |
|
| 643 |
0.034 2013-05-11 T. R. Wyant |
| 644 |
Correct spelling and grammar errors in POD and comments. RT #85050. |
| 645 |
Thanks David Steinbrunner for catching these. |
| 646 |
|
| 647 |
Allow interpolation in regex sets. It implies Perl 5.17.9 or higher. |
| 648 |
|
| 649 |
Allow non-ASCII white space under /x. It implies Perl 5.17.9 or |
| 650 |
higher. |
| 651 |
|
| 652 |
Fix problems with Regex Set functionality under Perl 5.6.2. CPAN |
| 653 |
testers RULE! |
| 654 |
|
| 655 |
0.031 2013-01-31 T. R. Wyant |
| 656 |
Have PPIx::Regexp::Token::Code (and offspring) become |
| 657 |
PPIx::Regexp::Token::Unknown inside a regex set. |
| 658 |
|
| 659 |
0.030 2013-01-22 T. R. Wyant |
| 660 |
Add Regex Sets, which were added to Perl as an experimental feature in |
| 661 |
5.17.8. This is experimental in Perl, therefore the parse may |
| 662 |
change. |
| 663 |
|
| 664 |
Ditch PPIx::Regexp::Token::GroupType method __expect_after_match() in |
| 665 |
favor of the more general __match_setup(). This is done without |
| 666 |
deprecation because __expect_after_match() was documeted as |
| 667 |
package-private, but noted in the change log because it _was_ |
| 668 |
documented. |
| 669 |
|
| 670 |
0.029 2013-01-14 T. R. Wyant |
| 671 |
Add method unescaped_content() to PPIx::Regexp::Element(). |
| 672 |
|
| 673 |
Rewrite the tokenizing code in PPIx::Regexp::Token::GroupType and |
| 674 |
offspring to use regular expressions specific to the regexp |
| 675 |
delimiter, and escaping only that delimiter. Thanks again to |
| 676 |
Alexandr Ciornii for finding more of these. |
| 677 |
|
| 678 |
Fix mis-parse of /(\?|I)/ as a branch reset (it's really an |
| 679 |
alternation). There may be more of these lurking. Thanks to Alexandr |
| 680 |
Ciornii for finding this one. |
| 681 |
|
| 682 |
Add options -files and -objectify to eg/predump. |
| 683 |
|
| 684 |
0.028 2012-06-06 T. R. Wyant |
| 685 |
Replace all uses of YAML::Any with YAML, since they come in the same |
| 686 |
distro, and YAML does not suffer from deprecation warnings. |
| 687 |
|
| 688 |
0.027 2012-05-28 T. R. Wyant |
| 689 |
Eliminate unescaped literal "{" characters in regexps in |
| 690 |
PPIx::Regexp::Token::Backreference and |
| 691 |
PPIx::Regexp::Token::CharClass::Simple. These are deprecated in 5.17.0. |
| 692 |
|
| 693 |
0.026 2012-02-24 T. R. Wyant |
| 694 |
Add support for \F (fold case), added in 5.15.8. |
| 695 |
|
| 696 |
0.025 2012-01-04 T. R. Wyant |
| 697 |
Tolerate leading and trailing white space around the regular |
| 698 |
expression. These are still round-trip safe, since the white space |
| 699 |
is tokenized. |
| 700 |
|
| 701 |
Make Changes file conform to CPAN::Changes, and add |
| 702 |
xt/author/changes.t to ensure continued compliance. |
| 703 |
|
| 704 |
0.024 2011-12-17 T. R. Wyant |
| 705 |
Reinstate author test xt/author/manifest.t, which was clobbered |
| 706 |
shortly before the release of 0.021_10. |
| 707 |
|
| 708 |
0.023 2011-12-08 T. R. Wyant |
| 709 |
Correct address of FSF in the version of the GPL distributed in |
| 710 |
LICENSES/Copying. Thanks to Petr Pisar for picking this up. |
| 711 |
|
| 712 |
0.022 2011-11-24 T. R. Wyant |
| 713 |
Correct various documentation errors. |
| 714 |
|
| 715 |
Don't initialize effective modifiers with '^', since that wrongly |
| 716 |
asserts that /d has been seen somewhere along the line. |
| 717 |
|
| 718 |
Implement negation of match-semantic modifiers (e.g. 'no re /u;') by |
| 719 |
setting the relevant datum to undef. |
| 720 |
|
| 721 |
Support for default modifiers. This includes: |
| 722 |
|
| 723 |
* default_modifiers argument to new() in PPIx::Regexp, |
| 724 |
PPIx::Regexp::Tokenizer, and PPIx::Regexp::Dumper |
| 725 |
|
| 726 |
* Public method modifier_asserted() on PPIx::Regexp, to return |
| 727 |
whether a given modifier is actually in effect. The results of the |
| 728 |
modifier() method are unchanged. |
| 729 |
|
| 730 |
Require Test::More 0.88 for installation. Eliminate all the 'eval |
| 731 |
{ require ... }' logic in favor of 'use Test::More 0.88'. |
| 732 |
|
| 733 |
Have Makefile.PL make use of {BUILD_REQUIRES} if it is available. |
| 734 |
|
| 735 |
Fix PPIx::Regexp::Token::Whitespace->can_be_quantified() to return |
| 736 |
false. |
| 737 |
|
| 738 |
0.021 2011-07-22 T. R. Wyant |
| 739 |
Modified tokenizer to correctly handle a back slash used as a |
| 740 |
delimiter. I believe. |
| 741 |
|
| 742 |
PPIx::Regexp::Dumper now dumps the results of ppi() if that method is |
| 743 |
present and -verbose is asserted. |
| 744 |
|
| 745 |
0.020 2011-04-02 T. R. Wyant |
| 746 |
Corrected perl_version_introduced(): |
| 747 |
|
| 748 |
* \R is now 5.009005 (was 5.000). |
| 749 |
|
| 750 |
0.019 2011-03-01 T. R. Wyant |
| 751 |
Various corrections to perl_version_introduced(): |
| 752 |
|
| 753 |
* \X is now 5.006 (was 5.000); |
| 754 |
|
| 755 |
* \N{name} is now 5.006001 (was 5.006); |
| 756 |
|
| 757 |
* \N{U+xxxx} is now 5.008 (was 5.006). |
| 758 |
|
| 759 |
The \C is now parsed as a PPIx::Regexp::Token::CharClass::Simple. It |
| 760 |
was previously considered a PPIx::Regexp::Token::Literal. |
| 761 |
|
| 762 |
Ensure that \N{$foo} parses as a Unicode literal, not a quantified \N. |
| 763 |
The ordinal() method returns undef for this. |
| 764 |
|
| 765 |
Understand the /aa modifier, introduced with 5.13.10. |
| 766 |
|
| 767 |
Report perl_version_introduced() of 5.013010 for the new semantic |
| 768 |
modifiers when modifying the entire expression. |
| 769 |
|
| 770 |
Correct handling of interpolations like ${^foo} and $#{foo}. |
| 771 |
|
| 772 |
0.018 2011-02-16 T. R. Wyant |
| 773 |
Override ppi() in PPIx::Regexp::Token::Interpolation to provide the |
| 774 |
proper PPI when variable names are bracketed. |
| 775 |
|
| 776 |
Properly parse bracketed variable names (I hope!), which may not be |
| 777 |
subscripted. |
| 778 |
|
| 779 |
Take account of possible '$' or '@' casts before a symbol in an |
| 780 |
interpolation (e.g. $$foo{bar}, which is equivalent to $foo->{bar}). |
| 781 |
|
| 782 |
Add the /a modifier to PPI::Regexp::Token::Modifiers, legal only in |
| 783 |
the (?:...) construction. This was introduced in Perl 5.13.9. |
| 784 |
|
| 785 |
When parsing an interpolation from a replacement string (rather than a |
| 786 |
regular expression), take subscripts at face value rather than |
| 787 |
trying to disambiguate them from quantifiers and character classes, |
| 788 |
which they can't be in this context. |
| 789 |
|
| 790 |
0.016 2011-01-05 T. R. Wyant |
| 791 |
The PPIx::Regexp::Token::Code perl_version_introduced() method now |
| 792 |
returns the minimum Perl version (currently set to 5.000) if it is |
| 793 |
used to represent the substitution portion of s///e. |
| 794 |
|
| 795 |
0.015 2010-10-25 T. R. Wyant |
| 796 |
Documented intent to revoke support for features introduced in a |
| 797 |
development Perl which do not make it to a production release. This |
| 798 |
is necessary because in this case the syntax could be reused with |
| 799 |
different semantics. |
| 800 |
|
| 801 |
Added support for Perl 5.13.6 (?^...) construction. |
| 802 |
|
| 803 |
Added support for Perl 5.13.6 d, l, and u modifiers. |
| 804 |
|
| 805 |
Fixed inconsistency in perl_version_introduced() results between |
| 806 |
PPIx::Regexp::Token::Modifier and |
| 807 |
PPIx::Regexp::Token::GroupType::Modifier. |
| 808 |
|
| 809 |
Corrected PPIx::Regexp::Constant RE_CAPTURE_NAME docs, somehow missed |
| 810 |
back at 0.010_01. |
| 811 |
|
| 812 |
0.014 2010-10-14 T. R. Wyant |
| 813 |
Recognize \o{...} as a PPIx::Regexp::Token::Literal, with |
| 814 |
perl_version_introduced() of 5.0013003. |
| 815 |
|
| 816 |
Terminate \0.. through \7.. after three characters, as Perl does. |
| 817 |
These two were brought to my attention by Brian D. Foy's "The |
| 818 |
Effective Perler" for October 11 2010, |
| 819 |
http://www.effectiveperlprogramming.com/blog/697 |
| 820 |
|
| 821 |
Correct the PPIx::Regexp::Token::Literal ordinal() method for '\b'. As |
| 822 |
a literal, this is a back space. |
| 823 |
|
| 824 |
0.013 2010-10-10 T. R. Wyant |
| 825 |
Declare a parse failure if characters are found between the '}' and |
| 826 |
the ')' of (?{...}) and (??{...}), and rebless the tokens to |
| 827 |
::Unknown. Perl does not accept anything here, so I think I should |
| 828 |
not either. |
| 829 |
|
| 830 |
Whitespace tweak in the PPIx::Regexp::Dumper test output for the |
| 831 |
failures test. |
| 832 |
|
| 833 |
Replace the PPI logic in PPIx::Regexp::Token::Code with a call to |
| 834 |
$tokenizer->find_matching_delimiter(). This is actually the way Perl |
| 835 |
works, as a look at toke.c and regcomp.c makes clear. |
| 836 |
|
| 837 |
Push the perl_version_introduced() back to 5.0 at the request of |
| 838 |
Alexandr Ciornii, for the potential benefit of Perl::MinimumVersion. |
| 839 |
This was done mostly by reading the various perlre, perldelta, and |
| 840 |
perlop documents, so these should be taken with a HUGE grain of |
| 841 |
salt. |
| 842 |
|
| 843 |
0.012 2010-09-26 T. R. Wyant |
| 844 |
Track all the features reported as introduced (or removed) in Perl |
| 845 |
5.010 back to Perl 5.009005, and report them as such. |
| 846 |
|
| 847 |
Report modifier /r as having been introduced in Perl 5.013002, rather |
| 848 |
than the default of 5.006. |
| 849 |
|
| 850 |
0.011 2010-09-16 T. R. Wyant |
| 851 |
Remove dependencies on Params::Util and Readonly. The latter was |
| 852 |
requested by ADAMK for the benefit of Padre. It involved changing |
| 853 |
the symbols exported from PPIx::Regexp::Constant, but these were |
| 854 |
documented as private, so ... |
| 855 |
|
| 856 |
Parse POSIX character classes [=a=] and [.a.] as |
| 857 |
PPIx::Regexp::Token::CharClass::POSIX::Unknown, which counts as a |
| 858 |
parse failure since these are not supported by Perl. |
| 859 |
|
| 860 |
Make the PPI::Document created by PPIx::Regexp::Token::Code->ppi() be |
| 861 |
read only. This means we need PPI 1.116. Cache the document, and |
| 862 |
ensure the cached result is returned on subsequent calls. |
| 863 |
|
| 864 |
0.010 2010-08-06 T. R. Wyant |
| 865 |
Fix fatal error in PPIx::Regexp::Token::Code->ppi(). |
| 866 |
|
| 867 |
Move author tests from xt/ to xt/author/. |
| 868 |
|
| 869 |
0.009 2010-08-03 T. R. Wyant |
| 870 |
Recognize s/.../.../ee as being different from s/.../.../e. In |
| 871 |
particular, the replacement portion of the former is _not_ a Perl |
| 872 |
expression: it's an interpolatble string, which later gets |
| 873 |
eval{}'ed. |
| 874 |
|
| 875 |
0.008 2010-07-01 T. R. Wyant |
| 876 |
Promote methods can_be_quantified() and is_quantifier() from |
| 877 |
PPIx::Regexp::Token to PPIx::Regexp::Element, so all classes inherit |
| 878 |
them. They still return true and false respectively. |
| 879 |
|
| 880 |
Override can_be_quantified() to return false on PPIx::Regexp, |
| 881 |
PPIx::Regexp::Structure::Quantifier, |
| 882 |
PPIx::Regexp::Structure::Regexp, and |
| 883 |
PPIx::Regexp::Structure::Replacement. |
| 884 |
|
| 885 |
Override is_quantifier() to return true on |
| 886 |
PPIx::Regexp::Structure::Quantifier. |
| 887 |
|
| 888 |
Modify PPIx::Regexp::Dumper to be able to display can_be_quantified |
| 889 |
and is_quantifier for PPIx::Regexp::Node objects when dumping |
| 890 |
verbosely. |
| 891 |
|
| 892 |
Convert internal data to Readonly in PPIx::Regexp::Lexer, |
| 893 |
PPIx::Regexp::Token::CharClass::Simple, |
| 894 |
PPIx::Regexp::Token::Structure, and PPIx::Regexp::Tokenizer. |
| 895 |
|
| 896 |
Remove leftover boilerplate in PPIx::Regexp::Token::CharClass::Simple. |
| 897 |
|
| 898 |
Explicitly require a minimum Perl of 5.006. |
| 899 |
|
| 900 |
Centralized dependencies in inc/PPIx/Regexp/Meta.pm. |
| 901 |
|
| 902 |
Removed claim that PPIx::Regexp is alpha code. Docs still say that the |
| 903 |
interface can be changed, but now it will go through a deprecation |
| 904 |
cycle. |
| 905 |
|
| 906 |
0.007 2010-04-28 T. R. Wyant |
| 907 |
PPIx::Regexp::Lexer no longer fails when encountering expressions like |
| 908 |
m{)}. Instead, it marks the right parenthesis as an unmatched |
| 909 |
delimiter. |
| 910 |
|
| 911 |
Fixed RT 56864 - PPIx::Regexp::Lexer fails in Perl::Critic under Perl |
| 912 |
5.13.0. This was due to the value of a returned $+[0] getting |
| 913 |
transmogrified before the caller saw it. I never did isolate what |
| 914 |
triggered the bug. |
| 915 |
|
| 916 |
You can now get a tokenizer trace by setting environment value |
| 917 |
PPIX_REGEXP_TOKENIZER_TRACE to a non-zero numeric value. This is |
| 918 |
unsupported, though. |
| 919 |
|
| 920 |
0.006 2010-02-26 T. R. Wyant |
| 921 |
Parse \N{...} in accordance with perl5115delta. The curlys must |
| 922 |
contain an alpha followed by alphanumerics, spaces, parens, colons, |
| 923 |
or dashes. \N{ without a matching } is a character class (if legal) |
| 924 |
followed by a literal '{'. |
| 925 |
|
| 926 |
Parse \N inside a character class as PPI::Regexp::Token::Unknown, |
| 927 |
since Perl 5.11.5 considers this a compile error. A \N{...} inside a |
| 928 |
character class is still OK. |
| 929 |
|
| 930 |
Add method match() to PPIx::Regexp::Tokenizer. This is analogous to |
| 931 |
capture(), but returns the entire matched string. |
| 932 |
|
| 933 |
0.005 2009-12-26 T. R. Wyant |
| 934 |
Recognize \N (without curlys), back-ported from Perl 6 into 5.11. |
| 935 |
|
| 936 |
Recognize unicode characters as \N{[[:alpha:]] ... rather than |
| 937 |
\N{[\w\s:] ... This is per the 5.11 documentation, but I think Perl |
| 938 |
always worked this way. |
| 939 |
|
| 940 |
Recognize loose matching of Unicode character classes, and allow '=' |
| 941 |
in lieu of a single ':' in a Unicode character class (this from Perl |
| 942 |
5.11.3). |
| 943 |
|
| 944 |
PPIx::Regexp::Dumper now produces the proper output when called with |
| 945 |
perl_version => 1, test => 1. |
| 946 |
|
| 947 |
Describe the typical content of the object in the documentation for |
| 948 |
PPIx::Regexp::Structure::NamedCapture and |
| 949 |
PPIx::Regexp::Token::GroupType::NamedCapture. |
| 950 |
|
| 951 |
0.004 2009-11-09 T. R. Wyant |
| 952 |
Have PPIx::Regexp::Token::Literal correctly recognize when |
| 953 |
charnames::vianame() is unavailable, and decouple this from the |
| 954 |
handling of \N{U+hhhh}. |
| 955 |
|
| 956 |
Add dependency on Task::Weaken, since depending on Scalar::Util |
| 957 |
appears not to cut it. |
| 958 |
|
| 959 |
Correct the assignment of the license type in Makefile.PL. |
| 960 |
|
| 961 |
0.003 2009-11-05 T. R. Wyant |
| 962 |
Have PPIx::Regexp::Token::Literal recognize \N{U+hhhh} (where hhhh |
| 963 |
represents hex digits), and provide its ordinal (hhhh). Remove |
| 964 |
recognition of \N. (. = any character), which Perl does not do. |
| 965 |
|
| 966 |
Fix $re->flush_cache() so that it actually removes $re and only |
| 967 |
$re from the cache. |
| 968 |
|
| 969 |
Add delimiters() method to PPIx::Regexp::Main and PPIx::Regexp. |
| 970 |
Support this in eg/prenav. |
| 971 |
|
| 972 |
Increase test coverage and remove dead code. |
| 973 |
|
| 974 |
Count tests in t/parse.t and t/unit.t |
| 975 |
|
| 976 |
0.002 2009-10-28 T. R. Wyant |
| 977 |
In verbose mode, have PPIx::Regexp::Dumper dump the absolute capture |
| 978 |
number referred to by a numbered reference. |
| 979 |
|
| 980 |
Have eg/preslurp pass its -verbose option to PPIx::Regexp::Dumper |
| 981 |
|
| 982 |
Don't use Test::More::isa_ok for the t/basic.t class heritage tests, |
| 983 |
since some versions of Test::More require a reference for the first |
| 984 |
argument of isa_ok(). |
| 985 |
|
| 986 |
0.001 2009-10-21 T. R. Wyant |
| 987 |
Initial release. |
| 988 |
|
| 989 |
# ex: set textwidth=72 autoindent : |