| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
The $type variable in typemaps is documented as in perlxstypemap as
"any : replaced with _", however currently it only does so in INPUT
sections. This will also make it do the same in OUTPUT sections.
|
|
|
|
| |
We pass these tests just fine on HPUX 11.31.
|
|
|
|
|
|
|
|
|
|
|
| |
Otherwise HPUX complains about unreachable statements.
"shared.xs", line 707: warning #2111-D: statement is unreachable
CLANG_DIAG_RESTORE_STMT;
^
This version should do the same thing, the only difference being
it doesnt allow a semicolon on the macro call.
|
|
|
|
|
|
|
| |
Otherwise on HPUX we get warnings
"threads.xs", line 1057: warning #2111-D: statement is unreachable
CLANG_DIAG_IGNORE_STMT(-Wthread-safety);
|
|
|
|
|
|
| |
Some of the HV logic uses a negative key length to indicate utf8
keys, and this logic was using an unsigned keylength, which obviously
does not work
|
|
|
|
|
|
|
|
|
|
| |
On HPUX we get a lot of:
"APItest.c", line 4004: warning #2111-D: statement is unreachable: PUTBACK
because people have used something like XSRETURN(1); and we generate
code that does PUTBACK; return; Adding a pragma to silence it makes the builds
happier;
|
|
|
|
|
|
|
|
|
|
| |
Module-CoreList was synced with CPAN and had its version in
Porting/Maintainers.pl updated. Module-CoreList was also updated
by running:
./perl -Ilib Porting/corelist.pl cpan
With some manual fixups afterwards to make it pass test.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The leading underbar is reserved by C.
These defines are debugging only "recursion" depth related counters
injected into the function macro wrappers when a function is marked as
'W', much the same way that aTHX_ and pTHX_ are when building under
threaded builds. The functions are expected to incremented the depth
parameter themselves. Note that "recursion" is quoted above because in
practice currently they are only used by the regex engine when recursing
virtually, and they do not relate to true C stack related recursion.
(But they could be used for tracking C level recursion under debugging
if someone needed it.)
|
| |
|
| |
|
|
|
|
|
|
| |
Fix INSTALLDIRS for perls after 5.10.
Add and update resource links.
|
|
|
|
| |
Makefile.PL taken from if 0.0608
|
| |
|
|
|
|
| |
CPAN::Changes or metacpan
|
|
|
|
|
| |
The CPAN dist uses Module::Install, so the Makefile.PL is rewritten to
use standard ExtUtils::MakeMaker.
|
|
|
|
|
|
|
|
|
|
|
| |
On a system with some sort of filesystem monitor such as a virus
scanner the atime of the file can be modified by that monitor
causing the test to fail.
Testers can set PERL_FILE_ATIME_CHANGES to a true value to avoid
comparing atime between the stat() and lstat() calls.
Fixes #19321
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The pod referred to a point as being in "frozen wastes". But that
judgement is a distraction from the point of the text, and not actually
true.
I looked at the spot in Google Maps. This area in the summer is
verdant, with many rivers and lakes. It is part of the
https://en.wikipedia.org/wiki/Putorana_Plateau. The closest place I
could (without expending much effort) find a non-satellite photograph
of is 60km away:
https://en.wikipedia.org/wiki/File:Putorana2._Lama_lake..jpg
Doesn't seem like a wasteland to me.
And for history buffs, the plateau contains part of the Siberian Traps,
remnants of volanic eruptions generally implicated as a cause of the
largest known extinction event, terminating the Permian.
|
|
|
|
|
| |
Minor changes to the Makefile.PL to point at the github repo for perl,
and cleaned trailing whitespace from Changes file.
|
|
|
|
|
|
|
| |
Minor changes to Makefile.PL: whitespace, INSTALLDIRS, and added a
require 5.006 as the module uses 'our', and removed some logic that is
thus redundant for building on perl versions earlier than 5.006. Also
changed license from 'perl' to 'perl_5'
|
|
|
|
|
|
|
|
| |
Minor tweaks to Makefile.PL to reflect that the file require 5.006,
so no need to do anything special for 5.005. Also fixed the LICENSE
field to be 'perl_5' and not 'perl'.
I did whitespace cleanup on Changes at the same time.
|
|
|
|
| |
Tweaked license to be 'perl_5' and not 'perl'.
|
| |
|
|
|
|
|
|
| |
Add Changes, Makefile.PL and examples directory.
Fixes this module for https://github.com/Perl/perl5/issues/20874
|
|
|
|
|
|
| |
Adds Changes, Makefile.PL, and examples/semaphore.pl
Fixes this module for https://github.com/Perl/perl5/issues/20874
|
|
|
|
|
|
| |
Fixes https://github.com/Perl/perl5/issues/20874 for this module
Tweaked Makefile.PL to set the license to 'perl_5' and not 'perl'
|
|
|
|
|
|
| |
This fixes this module for https://github.com/Perl/perl5/issues/20874
Tweaked Makefile.PL to set the LICENSE to 'perl_5' and not 'perl'
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a Makefile.PL for Attribute-Handlers in core so that it can be
maintained properly. This avoids the need for an external repo to
maintain these extra files.
Taken from Attribute-Handlers-0.99, with the following modifications:
- install in site, not perl
- Fix license, and don't try to handle ancient perl or EUMM versions
- update metadata URLs
- no indexing demo directory
|
|
|
|
|
|
|
|
| |
Fixes this module for https://github.com/Perl/perl5/issues/20874
Note the Makefile.PL was tweaked a bit to install into the right place
depending on version, and with an added comment. There are some very
old perls listed here.
|
|
|
|
|
|
|
| |
For some reason the CPAN module is not properly indexed. It is
https://metacpan.org/release/SBURKE/I18N-LangTags-0.35.
This fixes this module for https://github.com/Perl/perl5/issues/20874
|
|
|
|
|
|
|
|
| |
Files copied from https://github.com/rurban/Net-Ping
with minor changes made to point at the perl5 repo as we are upstream,
also changed the INSTALLDIRS rule to make the other files.
This fixes the module for https://github.com/Perl/perl5/issues/20874
|
|
|
|
| |
Fixes https://github.com/Perl/perl5/issues/20874 for this module
|
| |
|
|
|
|
|
| |
Yes, "or about 69 N 89 E, in the frozen wastes of Siberia."
but must reveal the crucial missing step involved!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Silences the following warning:
In file included from HiRes.xs:23:
./ppport.h:14832:1: warning: unused function 'DPPP_my_ck_warner' [-Wunused-function]
DPPP_(my_ck_warner)(pTHX_ U32 err, const char *pat, ...)
^
./ppport.h:11568:21: note: expanded from macro 'DPPP_'
#define DPPP_(name) DPPP_CAT2(DPPP_NAMESPACE, name)
^
./ppport.h:11567:24: note: expanded from macro 'DPPP_CAT2'
#define DPPP_CAT2(x,y) CAT2(x,y)
^
../../config.h:1387:19: note: expanded from macro 'CAT2'
#define CAT2(a,b) PeRl_CaTiFy(a,b)
^
../../config.h:1385:27: note: expanded from macro 'PeRl_CaTiFy'
#define PeRl_CaTiFy(a, b) a ## b
^
<scratch space>:34:1: note: expanded from here
DPPP_my_ck_warner
^
1 warning generated.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Silence warning about PL_parser. As far as I can tell we do not use it.
In file included from ../../perl.h:28,
from Storable.xs:16:
ppport.h:11564:26: warning: ‘DPPP_dummy_PL_parser’ defined but not used [-Wunused-variable]
11564 | # define DPPP_NAMESPACE DPPP_
| ^~~~~
../../config.h:1385:27: note: in definition of macro ‘PeRl_CaTiFy’
1385 | #define PeRl_CaTiFy(a, b) a ## b
| ^
ppport.h:11567:24: note: in expansion of macro ‘CAT2’
11567 | #define DPPP_CAT2(x,y) CAT2(x,y)
| ^~~~
ppport.h:11568:21: note: in expansion of macro ‘DPPP_CAT2’
11568 | #define DPPP_(name) DPPP_CAT2(DPPP_NAMESPACE, name)
| ^~~~~~~~~
ppport.h:11568:31: note: in expansion of macro ‘DPPP_NAMESPACE’
11568 | #define DPPP_(name) DPPP_CAT2(DPPP_NAMESPACE, name)
| ^~~~~~~~~~~~~~
ppport.h:12222:18: note: in expansion of macro ‘DPPP_’
12222 | static yy_parser DPPP_(dummy_PL_parser);
| ^~~~~
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Multiple forms of syntax can be used to obtain a package name from
`caller`, which emits this as its first return value, and assign
that name to a lexical scalar.
The following each achieve the same result, but with varying efficiency:
* `sub callme { my $package = caller(2); ...}`
* `sub callme { my ($package) = caller(2); ...}`
* `sub callme { my $package = (caller(2))[0]; ...}`
In the first example, `pp_caller` determines only the package name
and pushes it to the stack. In the other two examples, the other 10 of
`caller`'s return values are calculated and pushed onto the stack,
before being discarded.
This commit changes non-CPAN-first instances of the latter two forms
in core to the first form.
Note: There is a special exception to the equivalence described above,
when caller is use in list context within the DB package. Such a
usage instance in regen/warnings.pl therefore remains unchanged.
|
|
|
|
|
|
|
| |
Its the usual issue, that an old PR that bumps a modules
version may look fine in CI as it does not look like a conflict
as another patch has bumped the version to the same number,
but cmp_version.t notices and complains
|
|
|
|
| |
By always including `ppport.h`, this simplifies both XS code and tooling around it.
|
| |
|
| |
|
|
|
|
| |
Changelog updated.
|
|
|
|
| |
Document $way default.
Fix for #20721.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GCC-12 seems to have a propensity to warning about maybe-uninitialized
variables a lot more than it should. Most of the cases I have looked
into it turns out to be a false positive, but at the same time, it is
pretty simple to fix this kind of thing, so just fix it so the darn
thing will shut up.
This one just initializes some variables to NULL at the start of a test
function.
Fixes the following (slightly elided) warning.
gcc-12 -c ... -Og -g ... -W -Wall RealPPPort.c
In file included from ../../perl.h:6197,
from RealPPPort.xs:31:
../../embed.h: In function ‘XS_Devel__PPPort_OpSIBLING_tests’:
../../embed.h:461:49:
warning: ‘lastkid’ may be used uninitialized [-Wmaybe-uninitialized]
461 | # define op_free(a)
Perl_op_free(aTHX_ a)
^~~~~~~~~~~~
RealPPPort.xs:1741:21: note: ‘lastkid’ was declared here
1741 | OP *lastkid;
| ^~~~~~~
Fixes Github Issue #20816
|
|
|
|
| |
Fixes sync discrepancies with CPAN
|
|
|
|
|
|
| |
Make it a close-bracket to pair with open-bracket.
Bump $VERSION in Math-Complex .pm files to keep porting tests happy.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Karl has reported that he has issues with t/29a_upcopy.t under parallel
builds. I can not see any file based race conditions, but I can see code using
alarm around a test I can easily imagine would be too short for a loaded box
running many tests in parallel. This patch allows the test to use 20 seconds
instead of 10 if TEST_JOBS or HARNESS_OPTIONS are defined in the environment.
Hopefully this fixes tests on Karls box.
In a previous commit Dave M raised this from 5 to 10 seconds, so lets double
it again and see if Karls errors go away.
In an abundance of caution I also adjusted the other two cases of using
alarm() in this file to use the same logic and produce similar style
error messages.
|
| |
|
| |
|