Permalink
Commits on Jun 12, 2014
  1. Update Compress-Raw-Zlib to CPAN version 2.065

      [DELTA]
    
      2.065 3 February 2014
    
          * [PATCH] resolve c++ build failure in core
            [#92657]
    
          * gcc -g3: final link failed: Memory exhausted
            [#88936]
    
    Fixed Conflicts:
    	Porting/Maintainers.pl
    	cpan/Compress-Raw-Zlib/Makefile.PL
    	cpan/Compress-Raw-Zlib/Zlib.xs
    	cpan/Compress-Raw-Zlib/lib/Compress/Raw/Zlib.pm
    	t/porting/customized.dat
    
    Signed-off-by: Reini Urban <rurban@x-ray.at>
    bingos committed with Feb 3, 2014
Commits on May 22, 2014
  1. Note that the minimum supported gcc (on Windows) is 3.4.5

    Earlier versions (from www.mingw.org, at least) will build perl, but have
    a linker bug that causes various tests to fail due to problems with
    SDBM_File.dll. See perl #121936 for details.
    
    (cherry picked from commit bf537ce)
    steve-m-hay committed May 22, 2014
Commits on May 14, 2014
  1. Add links for perl bug tickets in previous commit

    (cherry picked from commit 47e6d4d)
    steve-m-hay committed May 14, 2014
  2. perldelta for #121676

    (cherry picked from commit 58627cd)
    bulk88 committed with steve-m-hay May 14, 2014
  3. Fix commit 2358a19

    Spotted by Daniel Dragan. We use GetEnvironmentStringsW() (deliberately so:
    see commit 4f46e52), so we must use FreeEnvironmentStringsW() to match.
    
    (cherry picked from commit a6abe94)
    steve-m-hay committed May 14, 2014
  4. [perl #121676] Fix memory leak in backticks and system

    Introduced by perl #113536. It doesn't actually leak on Windows XP due to
    differences in the implementation of GetEnvironmentStringsW() compared to
    later OSes, but the missing FreeEnvironmentStrings() was technically wrong
    anyway, and does now bite. Thanks for Daniel Dragan for finding this.
    
    (cherry picked from commit 90674ea)
    steve-m-hay committed May 13, 2014
Commits on Apr 16, 2014
  1. perldelta for 2396ba2

    tonycoz committed Apr 16, 2014
  2. copy xhv_rand and xhv_last_rand in threads clone

    valgrind complains about these fields being uninitialised when cloned into a
    new thread, because they aren't copied. It's fairly harmless, since these
    fields are just used to perturb hash key iteration; but for completeness,
    clone these fields too.
    
    Conflicts:
    	sv.c
    iabyn committed with tonycoz Feb 28, 2014
  3. perldelta for 2c60386

    tonycoz committed Apr 16, 2014
  4. [perl #119949] Stop undef *_, goto &sub from crashing

    Commit 049bd5f fixed problems with the wrong @_ being visible
    after *_ modification followed by goto.  In so doing, it made it
    possible for a null to be placed at the start of the target sub’s
    pad, because it was not checking that the array it got from PL_defgv
    was actually non-null.  Simply adding the check makes everything work.
    
    Conflicts:
    	t/op/goto.t
    Father Chrysostomos committed with tonycoz Jan 19, 2014
Commits on Apr 7, 2014
  1. perl5182delta typo fixes

    Escaping fix.
    
    Missing full stop added.
    
    (cherry picked from commit 2e061f0)
    Smylers committed with steve-m-hay Apr 2, 2014
Commits on Mar 8, 2014
  1. RT #119125: fix two issues with/[#]/x

    (This is a maint-specific patch, not a cherry-pick from blead)
    
    A hash within a character class in an expanded pattern is an odd beast.
    It is handled twice, first by the perl toker, which is looking for
    things like embedded variables that need interpolating, and second by the
    regex parser. The toker only has limited knowledge of regex syntax,
    and struggles to work out for things like /#$foo/x and /[#$foo]/x,
    whether that's a regex comment and so whether '$foo' is part of the
    comment string or a variable to be interpolated.
    
    Up until 5.18.0 inclusive it got very confused when the '#' was within a
    character class, and usually got it wrong. 5.18.0 also introduced the
    additional complication that (?{}) code-blocks were now normally handled
    by the perl toker rather than by the regex parser. A side-effect of this
    was that if for any reason the toker didn't spot a code block (because it
    erroneously thought it was part of regex comment for example), then the
    literal code block text would be passed through uncompiled to the regex
    parser, which would then refuse to compile unless "use re eval" was in
    scope.
    
    Al these problems have been fixed in blead. However, the fixes couldn't be
    fully back-ported to maint, since there was a fair bit of code on CPAN
    that would (erroneously) do things like /[#$^]/ which the author expected
    to match one three special characters, and indeed does on on older perls.
    On bleed however, this (correctly) expands to /[#STDOUT_TOP]/ (based on
    what $^ is currently set to). So we decided to keep the old (broken)
    behaviour on maint.
    
    These fixes and half-fixes were included in 5.18.2. However, it turns
    out that 5.18.2 still has a couple of issues, one of which is a regression
    from 5.16.x. The table below shows the behaviours of certain regex
    constructs under various flavours of perl. "5.18.3" represents the changes
    included in this commit, and the entries marked "*******" represent
    changes in behaviour since 5.18.2 (i.e. they are what this commit fixes).
    
    /[#$b]/x
    
        5.16.3 - $b not expanded
        5.18.0 - $b not expanded
        5.18.2 - $b not expanded - keep bug for backwards compatibility
        5.18.3 - $b not expanded - keep bug for backwards compatibility
        blead  - $b expanded
    
    /[#]$c/x
    
        5.16.3 - $c not expanded
        5.18.0 - $c not expanded
        5.18.2 - $c not expanded
        5.18.3 - $c expanded *******
        blead  - $c expanded
    
    /[#]
    (?{})/x   # i.e. this pattern includes a literal newline
    
        5.16.3 - re eval not needed
        5.18.0 - re eval needed
        5.18.1 - re eval needed
        5.18.2 - re eval needed
        5.18.3 - re eval not needed *******
        blead  - re eval not needed
    iabyn committed with rjbs Feb 18, 2014
Commits on Feb 22, 2014
Commits on Jan 13, 2014
  1. perldelta for 538acd8

    tonycoz committed Jan 13, 2014
  2. Crash in tab completion with Term::ReadLine::Gnu.

    Perhaps it also affects Term::ReadLine::Perl / Term::ReadLine::Perl5 .
    I still need to test with PadWalker installed. No tests were added, but
    it passes all existing tests.
    
    Conflicts:
    	lib/perl5db.pl
    shlomif committed with tonycoz Dec 19, 2013
  3. add new stub perldelta for 5.18.3

    rjbs committed Jan 13, 2014
Commits on Jan 7, 2014
  1. fix typo in perldelta

    rjbs committed Jan 7, 2014
  2. correct release date for v5.18.2

    rjbs committed Jan 7, 2014
Commits on Jan 6, 2014
  1. Update META files

    rjbs committed Jan 6, 2014
Commits on Dec 21, 2013
  1. add haarg to AUTHORS

    rjbs committed Dec 21, 2013
  2. bump to RC4

    rjbs committed Dec 21, 2013
  3. bump version on B::Concise

    rjbs committed Dec 21, 2013
  4. Update README copyright to 2013

    For RT #119625.
    
    (cherry picked from commit a271a37)
    Smylers committed with rjbs Sep 6, 2013
  5. update the super quick patch guide

    This is an import of the blead perlhack.pod from blead,
    with changes made by Smylers <Smylers@stripey.com> and
    detailed in [perl #119599].
    rjbs committed Dec 20, 2013
  6. Restore perlrepository.pod in stub form

    Give Perl doc sites a sane ‘latest’ version to display, directing readers
    to current information, rather than showing the Perl 5.12 version in
    perpetuity.
    
    And help anybody typing man perlrepository find where the docs have moved
    to.
    
    Suggested by Father Chrysostomos in:
    http://www.nntp.perl.org/group/perl.perl5.porters/2013/09/msg207079.html
    
    (cherry picked from commit 5edbc4f)
    Smylers committed with rjbs Sep 3, 2013
  7. Fix segfault in filehandle duplication

    Previously PerlIOBase_dup didn't check if pushing the new layer succeeded
    before (optionally) setting the utf8 flag. This could cause
    segfaults-by-nullpointer.
    
    (cherry picked from commit df8c7de)
    Leont committed with rjbs Sep 7, 2013
  8. Fix buffer overflow with overlong identifiers

    This was introduced by commit 3283393 in 5.17.10.
    
    $  ./perl -Ilib -e Foooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
    Identifier too long at -e line 1.
    Segmentation fault: 11
    
    (That was an amusing use of macro parentheses for the while condition,
    at least while it lasted.)
    
    (cherry picked from commit eaaaaa3)
    
    Conflicts:
    	t/comp/parser.t
    Father Chrysostomos committed with rjbs Sep 9, 2013
  9. Don’t assume targs are contiguous for ‘my $x; my $y’

    In commit 18c931a, the padrange optimisation was prevented from mak-
    ing this assumption for ‘my ($x,$y)’, but the assumption was still
    there in the code that combines multiple statements into one.
    
    This would lead to assertion failures (or, as of ce0d59f, crashes
    under non-debugging builds) if a keyword plugin declined to handle
    the second ‘my’, but only after creating a padop.
    
    This fixes a regression from 5.16 affecting Devel::CallParser under
    threaded builds.
    
    (cherry picked from commit 7601007)
    Father Chrysostomos committed with rjbs Sep 2, 2013