| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
This should resolve #92610.
|
| |
|
| |
|
|
|
|
| |
(Plus move comment from perldelta.pod to perl5124delta.pod)
|
|
|
|
| |
(Removed the change to patchlevel.h - Leon)
|
|
|
|
| |
(cherry picked from commit 899e5457ebe2dcf2d30225838d4b76e63283b67c)
|
|
|
|
|
| |
nice, zealous porting tests
(cherry picked from commit 69930b1860ecb5c4bddc59bb2ee41e5cea977545)
|
|
|
|
| |
(Removed the change to patchlevel.h - Leon)
|
|
|
|
| |
(cherry picked from commit f3fd521e97e17e487d338c4534dfc6b72ddb4e06)
|
|
|
|
| |
(cherry picked from commit 45492fbf291385039604f07b6acf0af0e069f654)
|
|
|
|
|
|
| |
Silenced the 'Can't call method "isa" without a package or object reference'
warnings for the functions.
(cherry picked from commit 95effdf194acae64a4ab711dc3d35da13872afdd)
|
|
|
|
|
| |
to silence cmp_version.t
(cherry picked from commit bede3d72c0bcc7540f7901cb14794032145ac4a5)
|
|
|
|
| |
(cherry picked from commit a0a0e5450c8a47684a1d0a4c7cb597974ad56ab1)
|
|
|
|
|
|
|
|
|
| |
I bumped this from 2.44 to 2.44_01 for 5.13.10 because that's what
Jesse did for 5.13.9, but that was an exceptional case:
<Bingos> it was a special case for v5.13.9 because of the v5.12.3
release being in the same week.
(cherry picked from commit 892528fd9702f80bc08486939e0831142045d6d9)
|
|
|
|
|
|
|
|
| |
Quoth Porting/release_managers_guide.pod:
"Also edit Module::CoreList's new version number in its F<Changes>
file."
(cherry picked from commit 071e5f376dca42e00a55b17ef8814b302b608f75)
|
|
|
|
|
|
| |
Update the CAVEATS section to mention 5.13.9 and 5.13.10. This was
forgotten around 5.13.9.
(cherry picked from commit 99537f099df1c72cb5e1d99f7cd7ca62f606d025)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I haven't updated the Changes and the META.yml file. This wasn't done
for 5.13.9, maybe it only needs to happen afterwards and
release_managers_guide.pod is wrong.
TODO: investigate that
Bumped to 2.44_01 (a dev release I don't expect to be CPANed on its
own). Doing it like Jesse Vincent in e0698539c3. Quoth
Porting/release_managers_guide.pod:
"Edit the version number in the new C<< 'Module::CoreList' =>
'X.YZ' >> entry, as that is likely to reflect the previous version
number."
(cherry picked from commit c552c5b5a692e78a154d3b045b80349665ef08fd)
|
|
|
|
|
| |
Raised as CPAN RT #65461 by Tokuhiro Matsuno
(cherry picked from commit 75081bb379696d31812ce0b07eded90b8395586c)
|
|
|
|
| |
(cherry picked from commit f1495101f8b951dc126f5898777a723f994cc6a4)
|
|
|
|
| |
(cherry picked from commit 96e4e4a039343538262e5d24133f0cd91cbc65a5)
|
|
|
|
|
|
|
| |
This was missed by change 57e52dbefae98516, which reverted 01bc7817c9b86c12,
because 5.12.3's release date was removed as an inadvertent side effect of
e0698539c3e1cd22, the change to add 5.13.9
(cherry picked from commit e1d797bc7c74f9b6c1234bd1b480120af21a0b37)
|
|
|
|
| |
(cherry picked from commit 57e52dbefae98516921f5d89cfa84d106fa34783)
|
|
|
|
| |
(cherry picked from commit 2926a53ca63a695a670f946c6ec92145e231813c)
|
|
|
|
|
|
| |
with 5.12.3 after discussions with BinGOs, I missed one place the version
number was defined.
(cherry picked from commit e83613b8c0c0665eb20ebe88e92e6b3d902b7892)
|
|
|
|
|
| |
v5.13.9 - Downgrade CoreList to 2.42_01 dev release.
(cherry picked from commit 01bc7817c9b86c128c93302fbb738d0f8ee28c3a)
|
|
|
|
|
|
|
| |
Bumped to 2.43_01 (a dev release I don't expect to be CPANed on its
own), since when we push to CPAN for 5.12.3, we'll have slightly
different data.
(cherry picked from commit e0698539c3e1cd2217300a97705a8636cb125079)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Everything is binary incompatible with each other, except for maint releases
from the same maint branch.
(cherry picked from commit c1b1cb88313395d8eb2084544a4f225116877020)
|
|
|
|
|
|
|
|
|
|
| |
As of Perl 5.12.0, the each(), keys() and values() functions also
operate on arrays, but were not listed in the table of contents section
titled "Functions for real @ARRAYs". This patch fixes that oversight.
The delete() and exists() functions were not added, as their use on
array elements has been deprecated.
(cherry picked from commit a5ce339cb0c533c90d1033581bf794417d495928)
|
|
|
|
|
| |
I will submit a similar patch upstream in a few days.
(cherry picked from commit 582bd8796b98142a11f99996b4e934a363b2cac0)
|
|
|
|
|
|
|
|
|
| |
A similar patch has been applied upstream. This will be overwritten
when the next CGI.pm is merged into blead, but at least we can get
the tests passing for now.
This does not affect any installed files.
(cherry picked from commit 5b898c5546fe02bdfea436d1c1091af7a890b187)
|
|
|
|
| |
(cherry picked from commit 108cd9378f43400cd4512da34871a49893a6f53d)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since f0e67a1 it was possible the freed buffer may be read from when
parsing a heredoc. This adds a call to lex_grow_linestr to grow the
buffer and ensure the pointers in PL_parser are updated.
The bug is pretty hard to reproduce, hence no test. I'm able to
reproduce it with the following:
perl -Meverywhere=re,debug -MParams::Util -e1
(cherry picked from commit 37c6a70c7d35357916da21616c68e56c878a5bd2)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The addition of the boolkeys op type in commit 867fa1e2d did not
account for the fact that rv2hv (%{}) can sometimes return undef
(%$undef with strict refs turned off).
When the boolkeys op is created (and the rv2hv becomes its kid), the
rv2hv is flagged with OPf_REF, meaning that it must return a hash, not
the contents.
Perl_softrefxv in pp.c checks for that flag. If it is set, it dies
with ‘Can't use an undefined value as a HASH reference’ for unde-
fined values.
This commit changes it to make an exception if rv2hv->op_next is a
boolkeys op. It also changes pp_boolkeys to account for undef.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The recent change to hints/linux.sh,
40f026236b9959b7ad3260fedc6c66cd30bb7abc
set the plibpth variable.
It was supposed to set all entries on a single line, but it didn't.
Do it now, and also remove trailing /'s.
(The collapsing is a more robust version of the previous commit,
since reverted, that davem wrote independently).
(cherry picked from commit bcab1245a0693be445ce018352f6fbe4abc26e88)
|
|
|
|
| |
perl5124delta.pod
|
|
|
|
|
|
|
|
|
|
|
| |
cryptographically secure due to concerns that end-users are unaware of
this and use it in situations where security depends on the strength of
the randomness generated.
I'd have been happier getting this patch in earlier in the cycle.
We'd hoped to replace the RNG, but that didn't happen in time, so this
doc update is the "better, still not good" fallback.
(cherry picked from commit 9700c45b7e3bd512c56a8c3607f53e73245de6db)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This bug was caused by change 28011 (ec9af7d), which stopped pp_lc
from using sv_setsv_flags, thereby bypassing these two lines at the
end of that function:
if (SvTAINTED(sstr))
SvTAINT(dstr);
Change 28012 (6730619) did exactly the same thing to pp_uc.
28013 (d54190f) broke ucfirst and lcfirst.
This commit simply puts that taint logic at the end of the pp_*
functions.
|
| |
|