| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
And in MMS or MMK on VMS it's a syntax error. So only spell it
with a dot when not using those utilities to run Devel::PPPort's
Makefile.PL.
|
|
|
|
|
|
|
|
|
|
|
| |
The current "no warranty" text warning against the use of Safe or
Opcode for "security purposes" is somewhat ambiguous. These modules
are not effective sandboxing mechanisms for evaluating untrusted
perl code and should not be used in that manner.
Safe and Opcode are, at best, hardening measures that could be used
in combination with operating system level sandboxing of the perl
interpreter.
|
|
|
|
|
|
|
|
| |
Instead, use an arbitrary path that has less chance of encouraging
people to allow the current directory in their path.
This was prompted by #16951 and attached as a patch to that issue which
was mistakenly closed without fixing the problem.
|
|
|
|
| |
..and Porting/corelist.pl warns about it
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Convert one 'else if' statement to a '#if' check
|
| |
|
|
|
|
| |
Note: VERSION was already bumped as part of e6aa2bc12e9cf0a0
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For example:
use Tie::Scalar;
use Data::Dumper;
sub T::TIESCALAR { bless {}, shift}
sub T::FETCH { die }
my $x;
tie $x, "T" or die;
while(1) {
eval { () = Dumper( [ \$x ] ) };
}
would leak various work SVs.
I start a new scope (ENTER/LEAVE) for most recursive DD_dump() calls
so that the work SVs don't accumulate on the temps stack, for example
if we're dumping a large array we'd end up with several SVs on the
temp stack for each member of the array.
The exceptions are where I don't expect a large number of unreleased
temps to accumulate, as with scalar or glob refs.
|
|
|
|
|
|
|
|
| |
these can leak if the value being dumped (or any part of it)
had get magic and that magic throws an exception.
Several other SVs can also leak in that case, but cleaning those up
is more complex.
|
|
|
|
|
| |
do this by mortalizing the SV on creation, rather than when we
push it on the stack
|
|
|
|
|
|
|
|
|
|
|
| |
Fix #17992
The test being skipped there is unreliable on windows.
Possibly @leonerd has a better idea, but in the meantime
I think it's fine to simply skip that one.
(cherry picked from commit 10e96ffd8a056ee32854ea3dcb89d99d9411ac67)
Signed-off-by: Nicolas R <atoomic@cpan.org>
|
|
|
|
|
|
| |
This is mainly restoring the PERL_BCDVERSION macro.
PERL_BCDVERSION is used by multiple CPAN distributions
and should not have been renamed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
89341f87 fix for GH #6799 introduced a regression when calling error()
on an IO::Handle object that was opened for reading a regular file:
$ perl -e 'open my $f, q{<}, q{/etc/hosts} or die; print qq{error\n} if $f->error'
error
In case of a regular file opened for reading, IoOFP() returns NULL and
PerlIO_error(NULL) reports -1. Compare to the case of a file opened
for writing when both IoIFP() and IoOFP() return non-NULL, equaled
pointer.
This patch fixes handling the case of the NULL output stream.
GH #18019
|
|
|
|
|
| |
Note that test files are not under file version
control anymore as they are generated files.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This was changed recently to avoid potential
warnings when using the variable outside of a BEGIN
block. As this is a non issue at this date,
let's restore the original syntax to avoid breaking
poor man parsing for VERSION which can exist somewhere.
References: #18024
|
|
|
|
|
|
|
| |
Use new core PERL_VERSION compare macros.
When bumping thread with this change
we would need to make sure to use the last
version of ppport.h
|
|
|
|
|
|
| |
When bumping Storable with this change
we would need to make sure to use the last
version of ppport.h
|
|
|
|
|
|
|
|
|
| |
These changes from Devel-PPPort are adding
support for Perl 7.0 and fixes the testsuite
with a Perl 7.0.0 binary.
We would have to publish a new version of
Devel-PPPort.
|
| |
|
|
|
|
|
|
|
| |
This is a partial revert to remove utf8->import
which breaks Storable
This reverts commit 894d8b10212a906402f4db9f9aac9efe9fa084fd.
|
|
|
|
|
|
| |
This code became irrelevant in 1996.
See https://github.com/Perl/perl5/pull/17658#pullrequestreview-377796612
|
| |
|
|
|
|
|
| |
This is a fixup for #17969 which wanted to load utf8_heavy.pl but
it is no longer available as of 5.31.6
|
|
|
|
| |
corelist --diff
|
|
|
|
|
|
|
| |
Fix #17992
This is preserving customized tests
and mark them as customized.
|
|
|
|
|
|
|
|
|
|
|
| |
Modules should have their version number directly in the module, not try
to pull it in from another module. The Exporter module that would be
loaded may not correspond to the Exporter::Heavy that is having its
version checked. Generally, pulling a version from another module would
fail on something like PAUSE or a CPAN client, but because Exporter is
probably already loaded, the old code would usually just pick the
version of the currently installed Exporter, rather than the one
corresponding to the Exporter::Heavy module that is being checked.
|
|
|
|
|
|
|
|
| |
* synchronize behavior with module documentation
IO::Socket docs states that passing Blocking => 0 will be set socket to non-blocking mode
* Update AUTHORS
* bump version
|
|
|
|
| |
and update the ChangeLog
|
|
|
|
|
| |
Similarly to GH #6799 clearerr() only cleared the error status
of the input stream, so clear both.
|
|
|
|
|
|
|
|
|
|
|
|
| |
For character devices and sockets perl uses separate PerlIO objects
for input and output so they can be buffered separately.
The IO::Handle::error() method only checked the input stream, so
if a write error occurs error() would still returned false.
Change this so both the input and output streams are checked.
fixes #6799
|
| |
|
| |
|
|
|
|
| |
Fixes GH #17271
|
|
|
|
|
|
|
|
| |
System perl on macOS also doesn't like linking libraries using relative
paths. The tests for ExtUtils::ParseXS already converted to absolute
paths on android, but it doesn't hurt to do that on all platforms.
Remove the platform conditional, and update the comment.
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
Make sure dist/IO is not using indirect
calls.
|
| |
| |
| |
| | |
This had its own copy of some macros that are now in core.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Rename some variables for clarity.
In one place, get() is returning a list, so we should test for contents of
list (via Test::More::is_deeply) rather than for string equality.
Signed-off-by: James E Keenan <jkeenan@cpan.org>
|
|/ |
|
| |
|