| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
future in the form of 5.13.0's release date)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Addresses a serious problem with CPANPLUS and behaviour of
version-0.82. Checking for out of date modules with 'o'
in CPANPLUS blows up if any modules that are installed
have non-numeric version strings.
Extract from Changelog:
Changes for 0.38 Fri Apr 23 15:52:38 BST 2010
=================================================
* New release of version raises exceptions on
parse errors. Use eval to guard ourselves
against this.
Changes for 0.36 Tue Feb 9 14:16:21 GMT 2010
=================================================
* Apply patch from Pavel Shaydo RT #53546 to improve
the performance of _parse_version()
|
|
|
|
| |
updates.
|
| |
|
|
|
|
|
|
| |
This reverts commit d98a0e0610723630e3a6cf6f1de20f87701b22bc.
Yeah, I'm an idiot.
|
| |
|
| |
|
|
|
|
|
|
|
| |
A bug in Porting/corelist.pl made Module::Corelist think the VMS::Filespec
module was called Filespec. This bug was fixed in
f4ccb67a0c5b6089da1ebe8b42943cf67d6c087a. This change updates all the old
corelist entries accordingly.
|
| |
|
| |
|
|
|
|
| |
kwalitee score.
|
| |
|
|
|
|
| |
Who knew there was a helper to do this, now!
|
| |
|
|
|
|
|
| |
This makes it easy to move through the file with { and } in vi.
Yes, this really helps.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
functions.
(cherry picked from commit 279018d8f7ee0701721a840ba1e85752012463bf)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
s+=UTF8SKIP(s) to move to the next char
Most of the regex code where do the two types of increments are wrapped up in macros.
Unfortunately these macros arent suitable in this case because we use goto to jump
inside the loop under some situations, and since this is a one-off case I figured the
modest C&P associated was better than creating a new macro just for this case.
There is still a possible bug here marked by an XXX, which will need to be fixed
once I find out the correct way to simulate strptr--. Additionally I havent found
a test case that actually exposes this form of the bug.
Moral of the story, utf8 makes string scanning awkward... And slow..
Cherry picked with trivial conflict resolution from v5.13.4-25-g92f3d48 (92f3d4829170316374b610b3fc665389803d93f8)
|
| |
|
|
|
|
|
|
|
| |
There's really no need to do this on the user side, as regcharclass.h is a real
file in the repository. Having this rule, while maybe handy for regexp
developers working on win32, otherwise only causes trouble if regcharclass.pl
changes in a way that doesn't require regcharclass.h to change.
|
| |
|
|
|
|
|
| |
Commit 32e653230c7ccc7f added this second argument, but didn't verify that the
stack always had sufficient space for it.
|
|
|
|
|
|
|
|
| |
Analogous to pp_getc and pp_tell in ac3697cd90b00fae, pp_eof has a conditional
POP from the stack, but an unconditional PUSH to the stack, but no check that
the stack had space for the PUSH. This bug has been present since perl 5.000.
(with slight tweak for maint to avoid tripping over the absence of 099be4f)
|
|
|
|
|
|
| |
Both conditionally POP a GV from the stack, but always PUSH a return value to
it. For the case where they did not POP the GV, they made no check that the
stack had space for the PUSH. This bug has been present since perl 5.000.
|
|
|
|
| |
(RT 43789: in memory" files don't call STORE)
|
|
|
|
|
|
|
| |
Currently we only compile the top level code with "extreme warnings", so code
in ext/ isn't subject to -Wdeclaration-after-statement, hence why this was
missed. Now that dual life modules have been evicted from ext/, we could
probably consider notching up the warnings for all code in ext/.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The code in PerlIO-scalar that implements the open $fh, '>' \$buffer
feature did not, apart from accidentally, support get/set magic and thus
tied buffers. This patch remedies that: mostly by just blindly sprinkling
SvGETMAGIC/SvSETMAGIC about, rather than doing any deep analysis and
understanding of the code. One main change I did was to add a
PerlIOScalar_read() function, rather than rely on the default behaviour
(which implements it in terms of PerlIOScalar_get_ptr() etc), since that
approach had a tendency to call FETCH multiple times
|
|
|
|
| |
reorganization)
|
|
|
|
|
|
|
|
| |
Change to start with "C<die> raises an exception." and phrase in terms of
handling exceptions, and then how uncaught exceptions result in process exit.
Do not give details of the exit code in the first paragraph. Move this to a
later paragraph, clarify that $! is often unpredictable, and stress that 255
is the last resort exit code.
|
|
|
|
|
|
| |
You can use (caller(0))[10} to retrieve the contents of %^H, and any
changes you make to your local copy will be lost, but that may not be
immediately apparent to the pod reader.
|
|
|
|
|
|
|
|
| |
The option seems to have been cargo-culted, as it is not
relevant to the Perl sources, and would really be useful
for 32-bit compiles only anyways (it detects certain
potential 64-bit compatibility issues in 32-bit compiles;
the 64-bit compilers always report these issues by default).
|
|
|
|
|
|
|
| |
The SDK2003SP1 compiler is special because it needs to link in
an additional bufferoverflow.obj file, which does not exist for
the other 64-bit MSVC compilers. This change un-breaks the
Makefle for all these other compilers (e.g. VS2008).
|
|
|
|
|
|
|
|
|
|
|
| |
Assignment of length() to a lexical is optimized by passing the
assigned-to variable as TARG, avoiding a pp_padsv and pp_sassign.
9f621b which changed length(undef) to return undef didn't take this into
account, and used SETs (which doesn't set TARG), so the code above left
$x == 3.
(cherry picked from commit d88e091f660036722622a815efa9ef3779605ea6)
(but hand-edited to adjust the test count)
|
|
|
|
|
| |
Otherwise it will be locked when trying to run it on VMS.
(cherry picked from commit ade9cf977f7d471077ecd475f145b736b50e9b52)
|
| |
|
| |
|
|
|
|
| |
'id -a' doesn't work, so try it without the -a if that fails.
|
|
|
|
| |
Signed-off-by: David Golden <dagolden@cpan.org>
|
| |
|
| |
|