| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Math::BigRat was trying to copy the sign of a BigRat object into a
BigInt object when converting to an integer, but without taking into
account that the number might be rounded toward zero. This resulted
in a 0 BigInt with a negative sign, which is not actually a valid
BigInt object, as it does not support negative zero.
|
|
|
|
|
| |
A link from the document to itself is not useful.
C<perldoc> should be L<perldoc>.
|
| |
|
|
|
|
| |
Upgrade version in Maintainers.pl.
|
|
|
|
|
|
|
|
|
| |
If we don't get that right, there may be additional semicolons in
the output C code. Those will be interpreted as empty statements
which is a problem for strict/old compilers which require strict
separation of declarations and other code.
Reported by Torsten Schoenfeld, diagnosed by Thorsten and Jan Dubois.
|
| |
|
|
|
|
|
|
| |
If XSUB.h/perl doesn't define the new XS_EXTERNAL macro that we
use for emitting non-static XSUBs for the boot functions, we have
XS_EXTERNAL just fall back to the standard XS macro.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This can be used to enable/disable the exporting of XSUB symbols.
Technically and at least as far as the documentation change is
concerned, this change goes together with the upcoming change
to XSUB.h to make not exporting the XSUB symbols the default.
It's harmless if a bit useless without that.
In the original plan for making XSUBs "static", there wouldn't have
been a public and easy way to make XSUBs exported from XS code
without resorting to manually redefining macros. But since even in
just the core set of modules, simple things break, I think it's best
to expose this bit of choice.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
and bump IO::Socket version.
|
|
|
|
|
|
|
|
|
|
| |
is busy or in non existing port
For non blocking socket, it a timeout has been specified, IO::Socket internally use select(..) to
detect the result of socket connection. In situation, where remote end is busy or in non-existing port, we spend
entire timeout mentioned in select(..) call. We cannot completely differentiate if error is WSAECONNREFUSED(10061) or
WSAETIMEDOUT(10060) in this situation. If we use the exception set in select(..) call, we can do early return and also
a make a clear differentiation in error condition. This is same like what Linux handle in this situation.
|
|
|
|
|
|
|
|
|
| |
select has a prototype of (;*), which is incorrect, as it implied that
it has high precedence. It also fails to account for the four-argu-
ment form. While removing all incorrect prototypes is counterproduc-
tive, I think this one is wrong enough it deserves to go. (And the
precedence problem is a good argument against it, as there is cur-
rently no other way to set precedence.)
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a follow-up to e4ac890e26c, which changed behavior from
appending to an existing MANIFEST to creating a new one. On VMS,
that would give us multiple versions, which probably wouldn't
matter except that the tests insist that there is one and only
one copy of every file they've created and they only clean up the
highest version.
The easiest way to handle this is to make sure we clean up first
before creating a new MANIFEST file.
|
|
|
|
|
|
| |
This reverts commit db147d7ee1c1aca547b1d63ef7141e56821a3ae2.
This is no longer necessary, as of this commit’s grandparent.
|
|
|
|
|
|
|
|
|
|
| |
If an XS paragraph/function definition that has a CODE section using
RETVAL, then we need an OUTPUT section or else things will go sour.
This adds a check for that condition and produces a friendly error
message.
See CPAN RT #69536.
|
| |
|
|
|
|
|
| |
I started to make Math::BigInt’s pod fit within 79 columns, but
soon petered out. At least this is better than nothing.
|
| |
|
| |
|
| |
|
|
|
|
| |
For the record: This was my (Steffen's) fault, not Mike's!
|
|
|
|
|
|
|
|
| |
The ExtUtils::ParseXS tests would sometime fail to locate some
core Perl typemaps in @INC. This fixes CPAN RT #70047.
Patch slightly modified by Steffen Mueller.
Includes the mandatory version bump to a development version.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This is ExtUtils::ParseXS 3.02. Nothing to see here.
|
| |
|
| |
|
| |
|
|
|
|
| |
(actually 79, so ‘comfortably within’ 80 columns)
|
|
|
|
|
|
| |
This commit re-indents the code examples in Attribute::Handlers
to make things more consistent overall and to prevent long lines
from wrapping in 80-column terminals.
|
|
|
|
|
|
| |
The tests were failing due to missing PERL_UNUSED_ARG.
This is an update to 3.00_05 from CPAN.
|
|
|
|
| |
(This is also the update to CPAN's 3.00_04).
|
|
|
|
|
|
|
|
|
| |
Both of these are attempts to fix win32 problems:
Bug #61908 for ExtUtils-ParseXS: MSWin compilers and back-slashed paths
Bug #53938 for ExtUtils-ParseXS: MinGW Broken after 2.21
Also bumps the version to 3.00_04.
|
| |
|
|
|
|
| |
Now at 3.00_03.
|
|
|
|
|
|
|
|
|
| |
There are reports of xsubpp failing to load the correct
ExtUtils::ParseXS. This adds some extra diagnostics.
Includes a minor doc-tweak.
Not perldelta worthy.
|
|
|
|
|
|
| |
With this new parameter, the current directory is not included in the
installed module search. This avoids finding modules from other perls
which happen to be below the current directory.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This will display the release date of a given perl release.
If no perl release is specified, will list all perl releases
and release dates.
|