| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
I've verified as fixed.
|
| | |
|
| |
|
|
| |
statements as C<function()>
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently PERL_ASYNC_CHECK is only called during scope exit in pp_leavetry
and pp_levaeeval. This means that if the signal handler calls die, the
eval won't catch it.
This broke Sys::AlarmCall's test suite, which was doing the equivalent of
$SIG{ALRM} = sub { die };
eval {
alarm(1);
select(undef, undef, undef, 10);
}
# expect the die to get caught and $@ set here.
Because the select was the last statement in the block, PERL_ASYNC_CHECK
wasn't called next until the leave_scope at the end of leavetry.
See RT #88774.
The simple fix is to add a PERL_ASYNC_CHECK at the top of
leavetry and leaveeval.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
The threads version for blead was bumped for the 5.13.11 release,
but not all version numbers were bumped, so the '1.83' in 5.14.0
will be marginally different (1 line of text) than in the 5.13.11 release.
|
| | |
|
| |
|
|
|
| |
Allow it to skip failing for particular versions of particular
modules
|
| |
|
|
| |
Test::Harness 3.23
|
| |
|
|
| |
I've pod-, spell-, and dupword-checked this.
|
| |
|
|
|
| |
• Mark it as experimental
• Remove paragraphs that no longer apply
|
| | |
|
| |
|
|
| |
This was ‘inadvertently’ fixed with commit 7ac5715
|
| |
|
|
| |
I broke this with commit d4fc441
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This pod misled some people, including this author, as to the initial
state of locales. This fleshes out some details, and changes some
wording.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This does a run-time check to see whether $scalar is a hash ref, and
dies if it is not.
This is to keep keys \@_ consistent with keys @_.
I cannot simply use OPf_MOD, since that indicates *potential* lvalue
context (including subroutine args).
So, instead, I take advantage of the fact that OPf_SPECIAL is always
set on the LHS of an assignment (usually to indicate that local()
should not erase the value).
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This no longer happens as of commit 7ac5715.
|
| |
|
|
| |
See ticket #80626.
|
| |
|
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
|
|
|
| |
This reverts commit 55e4a474ad63535e486bd657f45b5339709cbcd3.
In improved version is coming next...
|
| |
|
|
|
|
|
|
| |
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,
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is old code in configpm to handle mulit-line entries in config.sh
along the lines of
plibpth='/lib/x86_64-redhat-linux/4.4.5/
/lib/../lib64/
/usr/lib/x86_64-redhat-linux/4.4.5/
/usr/lib/../lib64/
/lib/
/usr/lib/'
which was broken, and produced
Use of uninitialized value $1
warnings, and messed up the content of lib/Config_heavy.pl.
We probably normally don't have multi-line entries, which is why no-one
noticed it before, but 40f026236b9959b7ad3260fedc6c66cd30bb7abc
has started generating the entry above.
|
| |
|
|
|
| |
Commit d4fc4415aac96132fac5b1e43e73bcba33a41b79 added two definitions
of the DEREF_PLAIN_ARRAY array; the non-GCC one had syntax errors
|
| |
|
|
|
|
| |
Reviewed section "Core Enhancements".
Signed-off-by: Ævar Arnfjörð Bjarmason <avar@cpan.org>
|
| |
|
|
|
|
|
| |
There were some places, where 'e.g.' was used without a comma. I made it
consistent.
Signed-off-by: Ævar Arnfjörð Bjarmason <avar@cpan.org>
|
| |
|
|
|
|
|
| |
There were more occurences of two spaces after full stops, so I made
those two that were only one.
Signed-off-by: Ævar Arnfjörð Bjarmason <avar@cpan.org>
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Clarify the note about qw(...) as parentheses deprecation. Without
being clarified this could be misunderstood to deprecate most uses of
qw(...).
This came up on the Git mailing list[1] after I submitted a patch[2]
to fix this issue in Gitweb[3].
1. http://permalink.gmane.org/gmane.comp.version-control.git/167293
2. http://permalink.gmane.org/gmane.comp.version-control.git/167283
3. http://permalink.gmane.org/gmane.comp.version-control.git/167297
|
| |
|
|
|
| |
Instead of just linking to L<feature> link to the "the
'unicode_strings' feature" section.
|
| |
|
|
| |
See ticket #80626.
|
| | |
|
