./devel/p5-PPIx-Regexp, Represent a regular expression of some sort

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 0.064, Package name: p5-PPIx-Regexp-0.064, Maintainer: pkgsrc-users

The purpose of the PPIx-Regexp package is to parse regular expressions
in a manner similar to the way the PPI package parses Perl. This class
forms the root of the parse tree, playing a role similar to PPI::Document.


Required to run:
[lang/perl5] [devel/p5-Task-Weaken] [devel/p5-List-MoreUtils] [devel/p5-PPI]

Required to build:
[devel/p5-Module-Build] [pkgtools/cwrappers]

Master sites: (Expand)

SHA1: 9b305eb267922762bad53e80d32e7411deff21db
RMD160: 603d3d4fe6a68563ab71c3759bd2763c724572d0
Filesize: 221.263 KB

Version history: (Expand)


CVS history: (Expand)


   2019-04-20 01:53:06 by Wen Heping | Files touched by this commit (2) | Package updated
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.
   2018-11-25 15:34:09 by Wen Heping | Files touched by this commit (2) | Package updated
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.
   2018-08-22 11:48:07 by Thomas Klausner | Files touched by this commit (3558)
Log message:
Recursive bump for perl5-5.28.0
   2018-08-21 13:13:27 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
p5-PPIx-Regexp: update to 0.062.

0.062		2018-08-12	T. R. Wyant
    Remove tokenizer method prior(). This is the last step in its
    deprecation.

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.
   2018-06-19 08:52:00 by Wen Heping | Files touched by this commit (2) | Package updated
Log message:
Update to 0.060

Upstream 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.
   2018-05-09 08:35:23 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
p5-PPIx-Regexp: update to 0.059.

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.
   2018-05-02 14:00:59 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
p5-PPIx-Regexp: update to 0.058.

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

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
   2018-03-11 11:19:49 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
p5-PPIx-Regexp: update to 0.056.

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.