Package Release Info

perl-PPIx-Regexp-0.082-bp154.1.13

Update Info: Base Release
Available in Package Hub : 15 SP4

platforms

AArch64
ppc64le
s390x
x86-64

subpackages

perl-PPIx-Regexp

Change Logs

* Tue Nov 30 2021 Tina Müller <timueller+perl@suse.de>
- updated to 0.082
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.082		2021-11-29	T. R. Wyant
    Add --version to eg/predump, and document all options with double
    dashes.
    Silence 'uninitialized' warning generated by /(?<=.{35})/.
    Thanks to Brian Fraser for reporting this.
    Try to quell weird Win32 test failures which seem to occur only in
    tests where I am using 'use open' to put the standard handles into
    UTF-8 mode. The fix (I hope) is to do this to the Test::Harness
    handles at run time instead of to the standard handles at compile
    time.
    Add file CONTRIBUTING.
* Sat Oct 23 2021 Tina Müller <timueller+perl@suse.de>
- updated to 0.081
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.081		2021-10-22	T. R. Wyant
    Any use of the postderef argument is now fatal.
    Correct generation of 'provides' metadata.  Thanks to Favio Poletti
    for blogging
    https://github.polettix.it/ETOOBUSY/2021/06/15/the-real-pause-workaround/,
    and ultimately to Joel Berger for the pointer to
    https://metacpan.org/pod/CPAN::Meta::Spec#no_index
    Add YAPE::Regex to SEE ALSO
* Sat Apr 17 2021 Tina Müller <timueller+perl@suse.de>
- updated to 0.080
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.080		2021-04-16	T. R. Wyant
    All uses of the postderef argument to new() now warn.
* Sat Mar 27 2021 Tina Müller <timueller+perl@suse.de>
- updated to 0.079
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.079		2021-03-26	T. R. Wyant
    Get prerequisites up to snuff, and add xt/author/prereq.t to ensure
    they stay that way.
    Add rt.cpan.org back to bug reporting methods. Long live RT!
* Fri Jan 29 2021 Tina Müller <timueller+perl@suse.de>
- updated to 0.078
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.078		2021-01-28	T. R. Wyant
    Allow CPAN to index Script_Run, Atomic_Script_Run, since they made
    it into a production release.
    Allow {,3} and { 0 , 3 } as quantifiers, requiring at least Perl
    5.33.6. Previously these parsed as literals. This parse will be
    retracted if it does not make it into 5.34.0.
* Fri Jan 15 2021 Tina Müller <timueller+perl@suse.de>
- updated to 0.077
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.077		2021-01-14	T. R. Wyant
    Add Travis CI testing.
    Use GitHub as bug tracker. R.I.P. rt.cpan.org.
* Sun Nov 29 2020 Tina Müller <timueller+perl@suse.de>
- updated to 0.076
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.076		2020-11-28	T. R. Wyant
    Correct (I hope) detection of \K in nested assertions.
    Variable-length look-behind is version 5.029009.
    Look-behinds quantified longer than 255 characters are an error, and
    are made into unknown tokens or structures. I ended up refactoring
    the PPIx::Regexp::Token::GroupType class initialization for the
    latter two changes.
* Fri Oct 09 2020 Tina Müller <timueller+perl@suse.de>
- updated to 0.075
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.075		2020-10-08	T. R. Wyant
    Warn on first use of attribute 'postderef'.
* Wed Sep 09 2020 Tina Müller <timueller+perl@suse.de>
- updated to 0.074
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.074		2020-09-08	T. R. Wyant
    Remove PPIx::Regexp::StringTokenizer itself and all documentation
    referring to it or the 'parse' argument to PPIx::Regexp->new().
* Wed Jul 29 2020 Tina Müller <timueller+perl@suse.de>
- updated to 0.073
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.073		2020-07-28	T. R. Wyant
    Remove prototypes from testing subroutines defined in t/*.t.
* Thu May 21 2020 Tina Müller <timueller+perl@suse.de>
updated to 0.072
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.072		2020-05-20	T. R. Wyant
    Drop dependency on List::MoreUtils.  Thanks to Graham Ollis
    (plicease) for bringing the issues with this module to my attention.
Version: 0.058-bp150.2.4
* Fri Apr 27 2018 coolo@suse.com
- updated to 0.058
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.058		2018-04-26	T. R. Wyant
    Prefer /[0-9]/ over /\d/ for numeric checks. The latter can match
    non-ASCII digits.
    Explain the negated POSIX character classes. Also tweak some of the
    asserted explanations -- mostly for readability and parallel
    construction with the negated explanations, but it turns out
    [[:digit:]] is NOT equivalent to [0-9].
* Wed Apr 18 2018 coolo@suse.com
- updated to 0.057
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.057		2018-04-17	T. R. Wyant
    Allow ->asserts( 'a*' ). This modification actually allows wild
    cards in asserts() on all match semantic modifiers, but it is
    probably only useful in the case of 'a*', because that is the only
    one that can be doubled.
    Explain grouping structure as 'Grouping', not 'Capture or grouping'.
    Caret modifier was not turning off /n. This was complicated by the
    fact that (?^) was introduced in 5.13.6, but (?n) was not introduced
    until 5.21.8. The solution was to include -n in the expansion of the
    caret if and only if /n had been seen in the scope of the caret.
    Recognize caret in /(?^)x/.
    Acknowledge Regexp::Parsertron in SEE ALSO
* Thu Mar 08 2018 coolo@suse.com
- updated to 0.056
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.056		2018-03-07	T. R. Wyant
    Support removal of unescaped literal left curlys after left parens,
    which was deprecated in 5.27.8. No actual change in output yet,
    since deprecation is not tracked, but the perl_version_removed()
    logic is there.
    Add next_element() and kin. These are analogous to next_sibling()
    and kin, but will cross over from content proper into structure
    (beginning and end delimiters, etc) and vice versa.
    Correct requirements_for_perl() for impossible regular expression.
    It now returns '! $]' when the components of the regexp are valid, but
    none are valid under any specific version of Perl. It used to think all
    Perls were OK when this happened.
    Add the alpha_assertions introduced in 5.27.9.
    Handle 5.27.9's change from +script_run to *script_run, and support
  * sr as a synonym.
* Mon Feb 12 2018 coolo@suse.com
- updated to 0.055
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.055		2018-02-08	T. R. Wyant
    Tokenizer method prior() is now fatal. This was documented as
    package-private, but as it WAS documented, I am putting it through a
    deprecation cycle anyway. Six months from now it will be removed.
    Add Script_Run classes as subclasses to their superclass docs. This
    was missed in the last update.
* Wed Feb 07 2018 coolo@suse.com
- updated to 0.054
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.054		2018-01-29	T. R. Wyant
    Add support for (+script_run:...). This is an experimental feature
    added in Perl 5.27.8. It imposes on any matches it contains the
    additional restriction that everything matched has to belong to the
    same Unicode script. This support will be retracted if the
    functionality does not make it into Perl 5.28.
    Add method scontent().  This returns significant content only. That
    is, if called on the parse of '/ f u b a r /x', it returns
    '/fubar/x'.
* Tue Oct 31 2017 coolo@suse.com
- updated to 0.053
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.053		2017-10-30	T. R. Wyant
    Recognize \px as Unicode char class. At least, when the x is C, L,
    M, N, P, S or Z.
    The 'parse' argument to new() is now deprecated.
* Mon Oct 09 2017 coolo@suse.com
- updated to 0.052
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.052		2017-09-07	T. R. Wyant
    RT 122715: Clarify Node->find_parents() documentation. Thanks to
    Salvatore Bonaccorso for letting me know about this problem..
    Further deprecate tokenizer method prior() in favor of
    prior_significant_token().
    Add requirements_for_perl(). This is analogous to the
    CPAN::Meta::Requirements method requirements_for_module(), though
    the output is formatted differently. Also put in the actual
    requirements for an un-escaped literal left curly after a constant,
    which was removed in 5.25.1 and reinstated in 5.27.1.
    Add accepts_perl(). This is analogous to
    CPAN::Meta::Requirements->accepts_module(). I decided that
    CPAN::Meta;:Requirements was overkill, but this may turn out to be
    the wrong decision, so I will be careful what I expose.
    Document behavior of perl_version_introduced() and
    perl_version_removed() when a feature is re-introduced after
    removal, or re-removed after re-introduction.
    \N{} (empty curlys) removed in 5.27.1.
* Mon Feb 13 2017 coolo@suse.com
- updated to 0.051
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.051		2017-01-29	T. R. Wyant
    Support whitespace inside [] if /xx in effect.
    Starting with Perl 5.25.9, a space or tab appearing inside a bracketed
    character class is not significant if /xx is asserted.
    Further deprecate tokenizer method prior()
    Add 'provides' data to ExtUtils::MakeMaker output
    SOME unescaped litaral '{' removed in 5.025001.
    After '.', Unicode classes, and bracketed classes (including extended)
    they are still legal.
    Make /{/ an error
    Perl fails to parse the above, because once it sees the '{' it wants
    to find one of the extended boundary assertions (like {wb}), and
    declares an error when it does not. So we check for this and rebless the
    curly into an unknown token, not a literal.
* Mon May 23 2016 coolo@suse.com
- updated to 0.050
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.050		2016-05-06	T. R. Wyant
    Parse bracketed substitution with embedded comment. This is something
    like s{foo}
  [#]{bar}
  {baz} which is equivalent to s/foo/baz/. PPI
    gets this wrong, and we're not smart enough to fix up the PPI parse,
    but if given this as text, we now parse it correctly.
    We now recognize postfix dereferences by default, since Perl does
    beginning with 5.24. In other words, default new() argument
    'postderef' to true.
    Unterminated substitutions (i.e. 's//') should no longer cause an
    exception. Instead they parse as an unknown token.
* Thu May 05 2016 coolo@suse.com
- updated to 0.049
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.049		2016-04-19	T. R. Wyant
    Robustify PPIx::Regexp->perl_version_removed()
    The problem here was that if the expression being parsed was
    sufficiently badly-formed, $self->delimiters() would be undef, throwing
    a warning.
    Correct dump of embedded modifiers (eg: (?i:...))
* Tue Mar 08 2016 coolo@suse.com
- updated to 0.048
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
* Sun Feb 07 2016 coolo@suse.com
- updated to 0.047
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.047		2016-01-29	T. R. Wyant
    No changes since 0.046_01.
  0.046_01	2016-01-22	T. R. Wyant
    Recognize {lb}, introduced in 5.23.7. If this is retracted before
    5.24, it will be removed outright.
* Wed Jan 13 2016 coolo@suse.com
- updated to 0.046
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.046		2016-01-08	T. R. Wyant
    Add GitHub repository to mmetadata.
* Sat Jan 02 2016 coolo@suse.com
- updated to 0.045
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.045		2015-12-31	T. R. Wyant
    No external changes since 0.044_01.
  0.044_01	2015-12-23	T. R. Wyant
    Deprecate tokenizer method prior() in favor of
    prior_significant_token(). This is not part of the public interface,
    so I suppose I could have just slam-dunked it, but ...
    Add ability to parse strings as well as regexes
    The new functionality is controlled by the new new() argument
    'parse', whose permitted values are 'regex' (the default), 'string',
    or 'guess'.  String parsing, and the 'string' and 'guess' values of
    'parse', are experimental.
* Wed Dec 09 2015 coolo@suse.com
- updated to 0.044
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.044		2015-12-08	T. R. Wyant
    No changes since 0.043_03.
  0.043_03	2015-12-01	T. R. Wyant
    Allow nesting of \Q with \U, \L, and \F
    The perlop docs say these nest with each other. Playing with Perl
    suggests that \U, \L and \F supersede each other, but thet they as a
    group nest with \Q in either order, so that if you specify \Q and
    one of the \U, \L, \F group you need two s to turn them all back
    off.
  0.043_02	2015-11-28	T. R. Wyant
    Restrict recognition of back references in replacement strings to
    number form, since Perl itself does not recognize \g{...} or
    \k{...} there.
  0.043_01	2015-11-25	T. R. Wyant
    Recognize postfix dereference if desired. This is controlled by the
    Boolean argument 'postderef' passed to PPIx::Regexp->new(). The
    default is false, but will become true if postfix dereference
    becomes mainstream Perl 5.
    Add explain() and supporting methods main_structure() and
    in_regex_set(). The explain() method returns a brief explanation of
    what the element does.
* Wed Nov 25 2015 coolo@suse.com
- updated to 0.043
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.043		2015-11-18	T. R. Wyant
    No changes since 0.042_05.
  0.042_05	2015-11-11	T. R. Wyant
    Do not end regex set prematurely on finding '])'
    The problem is that '])' can occur within an extended bracketed
    character class if it contains grouping parentheses and the last
    item in a group is a regular bracketed character class and there is
    no white space between the end of the character class and the end of
    the group.
    Record parse failure if switch condition is unknown
    The structure was being reblessed to
    PPIx::Regexp::Structure::Unknown, but the number of parse failures
    was not being incremented.
  0.042_04	2015-11-10	T. R. Wyant
    Parse \U and friends as meta-characters inside \Q...
    This turns out to be what Perl itself does, as shown by
    $ perl -E 'say qr{\Qoo}'
  0.042_03	2015-11-05	T. R. Wyant
    Clear error when lexer identifies unknown token. Those who peruse the
    changes in this release will see that a bunch of refactoring was
    done as part of this.
  0.042_02	2015-10-31	T. R. Wyant
    Parse white space inside bracketed character classes inside extended
    bracketed character classes (whew!) as literals, except for the
    space character itself and the horizontal tab. This tracks the
    corresponding change in Perl 5.23.4. This will be reverted if the
    corresponding Perl change does not make it into 5.24.0.
  0.042_01	2015-10-29	T. R. Wyant
    Beginning with version 0.035, PPIx::Regexp was incorrectly reporting
    the sense of modifiers when the same token both asserted and negated
    modifiers (e.g. '(?x-i:...)'). This release should correct the
    problem.
    Document policy when Perl changes in such a way that the proper parse
    for a regular expression changes. In this case the more modern parse
    is preferred.
* Sat Oct 10 2015 coolo@suse.com
- updated to 0.042
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.042		2015-10-09	T. R. Wyant
    No changes since 0.041_03.
  0.041_03	2015-10-01	T. R. Wyant
    Report error rather than failing when parsing a string consisting
    wholly of white space.
  0.041_02	2015-09-29	T. R. Wyant
    Group types were not being recognized if they contained the delimiter
    character for the regexp (e.g. in qr<(?\<foo)> the look-behind
    assertion was not recognized as such).
    Correct mis-parse of ' s///'. Leading white space is supposed to be
    acceptable, but the leading whitespace token caused
    PPIx::Regexp::Lexer not to recognize the substitution as such.
    Tokenizer was failing when the string to be parsed was so bad it was
    trying to return the whole thing as a single
    PPIx::Regexp::Token::Unknown.
    PPIx::Regexp::Dumper now displays a message if a structure is missing
    its end delimiter.
  0.041_01	2015-09-28	T. R. Wyant
    RT 107331 Produce parse error in the presence of trailing cruft.
    Thanks to Klaus Rindfrey for catching this.
    The tokenizer now does a preliminary scan for delimiting brackets
    and modifiers. Anything after the modifiers except for white space
    is now made into a PPIx::Regexp::Token::Unknown, resulting in a
    parse failure being reported. The previous implementation simply
    assumed a valid expression, and in the case of the expression in the
    ticket blithely mismatched the delimiters and returned a parse
    without failures, but which was manifestly bogus.
    Tweak documentation in PPIx::Regexp.
* Sat Jul 04 2015 coolo@suse.com
- updated to 0.041
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.041		2015-07-02	T. R. Wyant
    No changes since 0.041_02.
  0.040_02	2015-06-25	T. R. Wyant
    Report \C (match octet) as removed in 5.23.0.
  0.040_01	2015-06-20	T. R. Wyant
    Accept non-ASCII whitespace under /x. The Whitespace object can be
    multiple characters; the perl_version_introduced() becomes
    '5.021001' if any of them is a code point above 127.
    The perl_version_removed() method now returns '5.021001' when called
    on a PPIx::Regexp object produced by parsing '?foo?' (match once
    without explicit 'm'). The object produced by parsing 'm?foo?' still
    returns the minimum Perl version.
* Sun Jun 07 2015 coolo@suse.com
- updated to 0.040
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.040		2015-05-31	T. R. Wyant
    No changes since 0.039_02.
  0.039_02	2015-05-24	T. R. Wyant
    Do not parse unadorned parentheses as capture groups when /n is in
    effect. Instead, they are parsed as PPIx::Regexp::Structure. Named
    captures appear to be unaffected by /n.
    Made a verbose dump a little more so. Specifically, dump
    max_capture_group where relevant, and display dumped values a bit
    more informatively.
  0.039_01	2015-05-23	T. R. Wyant
    Report /n (no captures) as having been added in 5.21.8.
* Tue Apr 14 2015 coolo@suse.com
- updated to 0.039
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.039		2015-04-02	T. R. Wyant
    No changes since 0.038_01.
  0.038_01	2015-03-26	T. R. Wyant
    Recognize nested subscripts in interpolation.
    Thanks to Andy Lester for finding this, which actually manifested in
    Perl-Critic-Policy-Variables-ProhibitUnusedVarsStricter. The problem is
    that the actual heuristics for finding the end of an interpolation are
    undocumented, and I missed this rather-obvious case.
    Add {g} (= {gcb})
  0.038		2015-03-09	T. R. Wyant
    No changes since 0.037_01.
  0.037_02	2015-03-01	T. R. Wyant
    Make {foo} into an unknown token (and therefore an error. This
    applies to {anything}, where 'anything' is anything bur 'gcb',
    'wb', or 'sb'.
  0.037_01	2015-02-25	T. R. Wyant
    Handle the boundary assertions introduced in Perl 5.21.9: '{gcb}'
    (grapheme cluster boundary), '{wb}' (word boundary), '{sb}'
    (sentence boundary), and the corresponding '\B{...}' constructions.
    Similar-looking things like '{foo}' are not recognized as
    assertions, and end up being literals.  This is less general than I
    usually make things, but was done against the possibility that
    (e.g.) '{foo}' might be introduced later, requiring
    perl_version_released() to return a different number. Any of these
    retracted prior to Perl 5.22.0 will simply be removed from
    PPIx::Regexp.
  0.037		2014-11-12	T. R. Wyant
    Have PPIx::Regexp::Structure::RegexSet POD recognize that the Perl
    docs (specifically perlrecharclass) now call this construction
    Extended Bracketed Character Classes, not sets.
  0.036_01	2014-11-04	T. R. Wyant
    Correctly mark the replacement portion of s///ee as code. Prior to
    this release it was parsed as though no /e were present.
    Make available the number of times a given modifier is asserted
    (except for the match semantics modifiers which get handled
    differently). See PPIx::Regexp::Token::Modifier->asserted() and
    PPIx::Regexp::Tokenizer->modifier() for details.
Version: 0.071-bp152.1.2
* Sun Mar 29 2020 <timueller+perl@suse.de>
- updated to 0.071
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.071		2020-03-28	T. R. Wyant
    Recognize wildcard Unicode names (Perl 5.31.10).
    Try to get correct line number in derived PPI. This is done by
    injecting "
  " as needed. The initial #line directive becomes "#line
    2", but is suppressed if I need to generate line 1.
    Improve normalization of content for ppi(). This involves the
    un-bracketing of things like ${foo}.
    Deprecate new() argument postderef. At this stage it is only
    documented as deprecated. In the first release after October 1 2020
    it will warn on the first use. Eventually it will be retracted, and
    postfix dereferences will always be recognized. This is the default
    behavior now.
    Add dump argument/option 'short' which, if true, causes leading
    'PPIx::Regexp::' to be removed from class names.
* Fri Feb 28 2020 <timueller+perl@suse.de>
- updated to 0.070
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.070		2020-02-27	T. R. Wyant
    Add index_locations option to PPIx::Regexp->new(). This defaults to
    true if the regexp is specified as a PPI::Element object. The
    locations are consistent with the containing PPI::Document.
    Add methods location(), column_number(), line_number(),
    logical_filename(), logical_line_number(), and
    visual_column_number() to PPIx::Regexp::Element. All return undef if
    the locations could not be determined.
    Add method statement() to PPIx::Regexp::Element. This returns the
    PPI statement containing the regexp element, or nothing if none.
    Add method is_matcher() to PPIx::Regexp::Element. This classifies
    objects as to whether they actually match something in the target
    string. Possible returns are true (they do), false but defined (they
    do not) and undef (no clue).
    Add methods first_token() and last_token() to PPIx::Regexp::Node.
    Add methods next_token() and previous_token() to
    PPIx::Regexp::Element.
* Sun Feb 09 2020 <timueller+perl@suse.de>
- updated to 0.069
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.069		2020-02-07	T. R. Wyant
    The PPIx::Regexp->new() 'parse' option is now fatal. This selected
    either string or regex parse. I consider the string parse a failed
    experiment. This is the latest step in removing it in favor of the
    PPIx::QuoteLike package.
* Wed Jan 22 2020 <timueller+perl@suse.de>
- updated to 0.068
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.068		2020-01-21	T. R. Wyant
    Expose PPIx::Regexp::Util::is_ppi_regexp_element()
    explain() on [[=x=]] now calls it a Character Equivalence.
    It's still a PPIx::Regexp::Token::CharClass::POSIX::Unknown (and
    therefore an error), though.
* Mon Sep 23 2019 FSchreiner@suse.com
- fixed control characters in changelog file
* Sat Aug 31 2019 <timueller+perl@suse.de>
- updated to 0.067
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.067		2019-08-30	T. R. Wyant
    \K was retracted in Perl 5.31.3, but only inside look-around
    assertions.
* Sat Aug 17 2019 Stephan Kulow <coolo@suse.com>
- updated to 0.066
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.066		2019-08-16	T. R. Wyant
    Fix broken POD, and add tests to ensure it remains fixed.
* Sun May 26 2019 Stephan Kulow <coolo@suse.com>
- updated to 0.065
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.065		2019-05-25	T. R. Wyant
    Quash undef error in __is_ppi_regexp_element() when passed a
    PPI::Token::Regexp::Transliterate
    Support proper version for qr'\N{name}'. Until 5.29.10 this
    construction failed to parse because it did not interpolate. But
    PPIx::Regexp blithely ignored this detail. As of 5.29.10, something
    like m'\N{LATIN CAPITAL LETTER L}' matches identically to m'L'. So I
    implemented introduction as of that version.
    Have explain() recognize Unicode property wildcards.
* Tue Apr 02 2019 Stephan Kulow <coolo@suse.com>
- updated to 0.064
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.064		2019-04-01	T. R. Wyant
    Empty \p{} should be an error.
    \x{} and \x{ non-hex } should be errors under "use re 'strict'"
    \o{} should be an error
    \o{ non-octal } should be an error under "use re 'strict'"
    Support wildcard Unicode property values. These were added in
    5.29.9.
    Add eg/find-variable-length-lookarounds
    Add convenience method extract_regexps(). This is a static method
    on PPIx::Regexp that takes as its argument a PPI::Document and
    manufactures PPIx::Regexp objects out of anything that parses to a
    regexp of some sort.
    Don't run illegal character tests before Perl 5.18 unless we're
    author testing, because they are noisy. I think the issue is not the
    Perl version per se, but the version of Unicode; Perl5180delta says
    it shipped with Unicode 6.2.
* Fri Nov 09 2018 Stephan Kulow <coolo@suse.com>
- updated to 0.063
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.063		2018-11-08	T. R. Wyant
    Silence weird-character parse tests and make them no longer
    author-only.
    Further deprecate 'parse' argument to new(). You now get a warning
    on each use.
* Tue Aug 14 2018 coolo@suse.com
- updated to 0.062
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.062		2018-08-12	T. R. Wyant
    Remove tokenizer method prior(). This is the last step in its
    deprecation.
* Tue Jul 10 2018 coolo@suse.com
- updated to 0.061
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.061		2018-07-09	T. R. Wyant
    Only standalone graphemes and non-characters allowed as delimiters
    starting with Perl 5.29.0.
    Non-ASCII delimiters started working in 5.8.3, so that is what
    perl_version_introduced() returns for them.
    Collateral with all this, accept word characters as delimiters, but
    only with at least one space between the operator and the expression
  - - that is, 'qr xyx' is OK, but 'qrxyx' is not.
* Sun Jun 17 2018 coolo@suse.com
- updated to 0.060
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.060		2018-06-16	T. R. Wyant
    \N{} now parses as the unknown token, not NoOp, regardless of the
    setting of 'use re qw< strict >;'. \N{} became unconditionally fatal
    in 5.28.0 (5.27.1, actually). The policy when the parse changes is
    to use the most-modern parse. Hence this change.
    As a side effect of this, the unknown token's explain() method now
    returns something -- normally the associated error.
    Add method remove_insignificant(). If the invocant isa Node, this
    returns a clone of the invocant with non-significant elements
    removed. Otherwise it returns either the invocant or nothing.
* Wed May 09 2018 coolo@suse.com
- updated to 0.059
  see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
  0.059		2018-05-08	T. R. Wyant
    Install @CARP_NOT everywhere so that warnings and exceptions
    generated in the bowels of the system appear to come from the point
    where the system is entered.
    Further deprecate string (versus regexp) parsing. The first use of
    the 'parse' argument to new() will result in a warning.  If the
    value of the argument is 'guess' or 'string', the warning refers to
    PPIx::QuoteLike.