In perl.git, the branch smoke-me/khw-regcomp has been created

<http://perl5.git.perl.org/perl.git/commitdiff/c168f18fb9ae4dce85f1926ddd0a68684d326a12?hp=0000000000000000000000000000000000000000>

        at  c168f18fb9ae4dce85f1926ddd0a68684d326a12 (commit)

- Log -----------------------------------------------------------------
commit c168f18fb9ae4dce85f1926ddd0a68684d326a12
Author: Karl Williamson <k...@cpan.org>
Date:   Mon Oct 12 16:38:32 2015 -0600

    PATCH: [perl #126180] /(?[\ &!])/ segfaults

M       regcomp.c
M       t/re/reg_mesg.t

commit b9e2eb2bb6ac8c4f0a56dd82d551a16f24e01bbc
Author: Karl Williamson <k...@cpan.org>
Date:   Mon Oct 12 12:31:58 2015 -0600

    qr/\p{pkg1::...foo}/ must be a user-defined property
    
    So, if it isn't found and 'foo' doesn't begin with 'In' or 'Is', we know
    that there would be a run-time error, which we can fail instead at
    compile time with.  We use a different error message than if we don't
    know if it is a user-defined property.
    
    See thread beginning at
    http://nntp.perl.org/group/perl.perl5.porters/231658

M       pod/perldiag.pod
M       regcomp.c
M       t/re/regexp_unicode_prop.t

commit b7b066a2172ff2791591c998b2ca92ab86edc092
Author: Karl Williamson <k...@cpan.org>
Date:   Mon Oct 12 12:29:41 2015 -0600

    regcomp.c: Add macro to output diagnostic
    
    This is like a similar macro, but takes an extra argument.  It will be
    used in the next commit

M       regcomp.c

commit 6269c5ac9e1f1a22497b1c84a20a5fb12f86c41c
Author: Karl Williamson <k...@cpan.org>
Date:   Mon Oct 12 12:29:14 2015 -0600

    regcomp.c: White-space, comments only

M       regcomp.c

commit 77075d181ac32318be8a92d422f2a49dd62e1ccd
Author: Karl Williamson <k...@cpan.org>
Date:   Mon Oct 12 12:20:33 2015 -0600

    perldiag: Remove no-longer used message.
    
    I noticed that this message was there, but hasn't been used for some
    time, having been replaced, and I didn't look too hard for when.

M       pod/perldiag.pod

commit cd9d11133dfa288085103ab8fba25a837b6a4617
Author: Karl Williamson <k...@cpan.org>
Date:   Mon Oct 12 11:42:27 2015 -0600

    podcheck.t: Regen db after recent new long verbatim line
    
    Commit 6fc2106e6704b632dc6ea04410ea89e1fa4ca43c added a verbatim line
    longer than 79 chars.

M       t/porting/known_pod_issues.dat

commit 536e6fae9b7ae30f884dc66039d126ceaa565c97
Author: Karl Williamson <k...@cpan.org>
Date:   Mon Oct 12 11:38:35 2015 -0600

    porting/maintainers.t: Skip if -DPERL_EXTERNAL_GLOB
    
    Maintainers requires the internal File::Glob.
    
    I also reordered the skip if VMS test so the skip tests are all adjacent.

M       t/porting/maintainers.t

commit 9dea0f90cfcb5a4baa9ef7d3d74b8ed32f801c9b
Author: Karl Williamson <k...@cpan.org>
Date:   Wed Oct 7 16:54:49 2015 -0600

    Fix \p followed by a non-alpha
    
    See threads beginning at
        http://nntp.perl.org/group/perl.perl5.porters/231263
        http://nntp.perl.org/group/perl.perl5.porters/231389
    
    Prior to this commit, these did not generate the pattern that would be
    expected, and displayed apparently irrelevant warnings.  Now this is a
    fatal error.
    
    This resolves [perl #126187].

M       pod/perldelta.pod
M       pod/perldiag.pod
M       regcomp.c
M       t/re/re_tests

commit e695c1cef0268d71d06a0020ffbf0371d7512b3a
Author: Karl Williamson <k...@cpan.org>
Date:   Wed Oct 7 16:42:37 2015 -0600

    regcomp.c: Make compile and run-time error msgs identical
    
    Prior to this commit, an unknown Unicode property gave different
    messages depending on when the problem was found.  Prior to the previous
    commit, most were found at run-time, but now most are found at
    compile-time.  Therefore use the runtime message everywhere, as it was
    the most often encountered before.

M       pod/perldiag.pod
M       regcomp.c
M       t/re/reg_mesg.t

commit 75f0e69211fb33125bb4e6200b48749cbb8a5648
Author: Karl Williamson <k...@cpan.org>
Date:   Wed Oct 7 16:39:07 2015 -0600

    regcomp.c: Find more errors at compile time
    
    Users can create their own Unicode-like properties, but the names of
    those must follow a very restricted syntax.  When compiling a property,
    if we can't find it, we have presumed it might be a user-defined one
    that will be known at runtime.  But if the name doesn't follow the
    restricted syntax, it can't be such, and so must be an error.  Abort now
    rather than waiting until run time.

M       regcomp.c

commit ccbd21c1555c25a92d88845d36c761ea965b1b0b
Author: Hugo van der Sanden <h...@crypt.org>
Date:   Fri Feb 27 10:54:24 2015 +0000

    XXX Remove SWASHNEW: check for empty type
    
    This avoids warnings when the supplied type consists only of whitespace.

M       lib/utf8_heavy.pl

commit af733454f129c23d9837b04666dff5602b392785
Author: Karl Williamson <k...@cpan.org>
Date:   Fri Sep 11 12:37:27 2015 -0600

    test.pl

M       t/test.pl
-----------------------------------------------------------------------

--
Perl5 Master Repository

Reply via email to