| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
The x2p and utils .PL extractions use the Cwd module, which is not
available in miniperl in a static build. (For a dynamic build, miniperl
only loads the pure perl portion of Cwd, but building the whole extension
ensures that the pure perl part is correctly built and available. It might
be cleaner just to always require the full perl.)
|
|
|
|
|
| |
XS-APItest-KeywordRPN has turned out to be less useful as an independent
module than expected, and less strictly about RPN than it originally was.
|
|
|
|
|
|
|
|
|
|
| |
It looks like h2ph makes copious use of global variables. As a result, I can
commit this evil for a minimal patch. No code was changed moving it into the
sub other than passing $proto, which is the only non-global used (but not
modified).
I tried a 5.12.0 build with this patch and it seems to be passing tests.
There is a lib/h2ph.t file but I don't know what it tests exactly.
|
|
|
|
| |
Both Ken and David agree with this.
|
|
|
|
|
|
|
|
|
|
| |
The code that guessed a default sender address would under some
circumstances not display this guess to the user with the option to change
it. Specifically, if $Config{cf_me} eq {login id of the user running
perlbug}.
In my case, cf_email got set at build time (Configure default) of
'davem@pigeon.(none)', which was then silently used. Not good!
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: H.Merijn Brand <h.m.brand@xs4all.nl>
|
| |
|
|
|
|
|
| |
This patch also make PERL_GIT_UNCOMMITTED_CHANGES useful and thus avoids
always adding the "*" to the 'perl -v' output.
|
|
|
|
|
| |
perlbug doesn't check the return status of Mail::Send and so reports
"Message sent" even if it hasn't:
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Date: Tue, 27 Oct 2009 01:29:40 +0000
From: Zefram <zefram@fysh.org>
To: perl5-porters@perl.org
Subject: bareword sub lookups
Attached is a patch that changes how the tokeniser looks up subroutines,
when they're referenced by a bareword, for prototype and const-sub
purposes. Formerly, it has looked up bareword subs directly in the
package, which is contrary to the way the generated op tree looks up
the sub, via an rv2cv op. The patch makes the tokeniser generate the
rv2cv op earlier, and dig around in that.
The motivation for this is to allow modules to hook the rv2cv op
creation, to affect the name->subroutine lookup process. Currently,
such hooking affects op execution as intended, but everything goes wrong
with a bareword ref where the tokeniser looks at some unrelated CV,
or a blank space, in the package. With the patch in place, an rv2cv
hook correctly affects the tokeniser and therefore the prototype-based
aspects of parsing.
The patch also changes ck_subr (which applies the argument context and
checking parts of prototype behaviour) to handle subs referenced by an
RV const op inside the rv2cv, where formerly it would only handle a gv
op inside the rv2cv. This is to support the most likely kind of modified
rv2cv op.
[This commit includes the Makefile.PL for XS-APITest-KeywordRPN missing
from the original patch, as well as updates to perldiag.pod and a
MANIFEST sort]
|
| |
|
|
|
|
|
| |
Move the shasum binary to the top level, to remove the need for a MAP entry in
Maintainers.PL
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Follow-up to b78fd7160df924147ff968f6dc2796473af0c484.
|
|
|
|
| |
Follow-up to 4822030c168a634e0e2adb4eaa6369019c959730.
|
|
|
|
|
|
|
|
|
|
| |
t/lib/TieOut.pm is now from Test::Simple.
Only the tests needed changing. The exceptions to BEGIN/PERL_CORE/INC
boilerplate removal were two instances of "../.." becoming "../../../..",
and changing an %INC test from "strict.pm" to "less.pm", as TestInit causes
strict to be loaded via a relative path, when it loads File::Spec to convert
all paths from relative to absolute.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
and add missing files from the CPAN distribution.
Also adjust utils/corelist.PL to look for the corelist utility in the
new directory.
|
|
|
|
| |
This fixes [perl #68682] : 5.10.1 ( RC1 and RC2 ) perlivp fails IO/Compress
|
| |
|
|
|
|
|
| |
but these days it contains macros that expand to patch lists;
for now, just skip these macros. need a proper fix sometime.
|
| |
|
|
|
|
|
|
| |
expr() contains a code to handle "defined(SYM)" in #if directives.
Unfortunately, this code is not executed for "defined SYM", without
parentheses. This patch fixes it.
|
|
|
|
|
| |
Also replaces lots of 5.00702 (note missing 0) with 5.006002. This is to
allow us to jettison Test.pm from core eventually.
|
|
|
|
|
|
|
| |
Where the user names a module that their bug report is about, and we know the
URL for its upstream bug tracker, provide a message to the user explaining
that the core copies the CPAN version directly, and provide the URL for
reporting the bug directly to upstream.
|
|
|
|
|
| |
$Config{ccsymbols} and friends are currently empty on Win32 and
undefined on VMS.
|
|
|
|
|
|
|
| |
As reported by Christopher Zimmermann in <http://bugs.debian.org/379757>,
code generated from simple #undef directives by h2ph can cause
'Constant subroutine ... undefined' warnings if the undefined
function was eligible for inlining.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Patch and description by Rainer Weikusat, forwarded from
http://bugs.debian.org/502297 :
The h2xs program scans C headers for 'constants' either defined
as preprocessor macros or via enum and builds a sorted list of names
containing the macros and enum values found in this way. This list
is then passed to ExtUtils::Constant::WriteConstants, which generates
the corresponding const-c.inc and const-xs.inc files when perl Makefile.PL
is executed. By default, ie when just processing a constant name, this
function assumes that the name refers to a preprocessor macro and
the generated C-code in const-c.inc contains conditional compilation
directives to either return the macro value or Perl_constant_NOTDEF,
depending on the defined'ness of the macro. This causes constants
defined as enumeration values to never be available to module users,
because they are not visible to the preprocessor.
Instead of passing just a name to the WriteConstants-routine, a
hashref (members documented in ExtUtils::Constant::Base(3perl))
can be used to specify more details regarding what code
should be generated for a particular constant. For an enumeration
value, a hashref constructed as
{ name => <name of the constant>, macro => 1 }
could be used to get rid of the inappropriate preprocessor
directives.
( Another version of the same fix was also submitted by Daniel Burr in
http://bugs.debian.org/320286 )
|
|
|
|
|
|
|
|
|
|
|
|
| |
As seen in <http://bugs.debian.org/522673>, since 4.2.0 or so
gcc's search path has a new "include-fixed" directory,
which currently contains <syslimits.h> and a few other headers.
Converting <syslimits.h> therefore fails unless h2ph knows about the new
directory too.
See http://gcc.gnu.org/ml/gcc-patches/2007-02/msg02038.html for some
background to the gcc change.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Contrary to the comment in the code, h2xs mishandles enums that
contain C++ style comments.
An example of a failing header:
enum {
A = -1, // negative one
// with more comments
B = -2, // negative two
C = -3 // negative two
};
which generates exported constants for 'A' and 'negative'.
The patch is slightly modified from the one by Daniel Burr in
http://bugs.debian.org/320286
|