Log message:
p5-PPIx-Regexp: update to 0.074.

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().

Log message:
p5-PPIx-Regexp: update to 0.073.

0.073		2020-07-28	T. R. Wyant
    Remove prototypes from testing subroutines defined in t/*.t.

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.

Log message:
*: bump PKGREVISION for perl-5.32.

Log message:
(devel/p5-PPIx-Regexp) Updated 0.67 to 0.71

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 "\n" 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.

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.

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.

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.

Log message:
(devel/p5-PPI-Regexp) Updated 0.065 to 0.067

0.067           2019-08-30      T. R. Wyant
    \K was retracted in Perl 5.31.3, but only inside look-around
        assertions.

0.066           2019-08-16      T. R. Wyant
    Fix broken POD, and add tests to ensure it remains fixed.

Log message:
Bump PKGREVISIONs for perl 5.30.0

Log message:
Update packages using a search.cpan.org HOMEPAGE to metacpan.org.

The former now redirects to the latter.

This covers the most simple cases where http://search.cpan.org/dist/name
can be changed to https://metacpan.org/release/name.

Reviewed by hand to hopefully make sure no unwanted changes sneak in.

Log message:
Update to 0.065

Upstream 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.

Log message:
Update to 0.064

Upstream 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.

Log message:
Update to 0.063

Upstream 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.