| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
Who knew there was a helper to do this, now!
|
|
|
|
| |
Notice the glorious deletion of Switch from the manifest!
|
| |
|
|
|
|
|
| |
This makes it easy to move through the file with { and } in vi.
Yes, this really helps.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
And tweak its documentation.
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
remove it in 5.15 in the Spring of 2011.
|
| |
| |
| |
| |
| |
| |
| |
| | |
removed in 5.14.
Revert "Remove Shell from the core distribution. Get it from CPAN now."
This reverts commit 28d302d426b73ed76fdcc816dd51bb1a8f93332b.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* 'blead' of ssh://perl5.git.perl.org/gitroot/perl:
Fix groups.t test on AIX
further fix for RT #23810
use the correct format codes in warnings from gmtime/localtime
Better perldiag heading for "\cX" deprecation warning
PATCH: Clean up EBCDIC handling of \cX
[perl #41530] s/non-utf8/is-utf8/ fails.
Fix for README.aix and XL C/C++ V11
|
| | |
| | |
| | |
| | | |
'id -a' doesn't work, so try it without the -a if that fails.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The fix for #23810, 27e904532594b7fb, introduced a regression, spotted by
Nicholas as RT #75146.
Basically, in S_doeval() if the yyparse() fails due to dying (rather than
just bailing out with with a syntax error, say), then the topmost EVAL
context will have been popped. My improved error handling code mostly
understood the difference, but forgot that in the die case, PL_eval_root
will have been restored to its previous value by the CX pop, and thus
its value shouldn't be messed with.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The function perl_ebcdic_control() is unnecessary, as the toCTRL macro
that calls it can be changed to just map EBCDIC to ASCII first, and then
doing the normal procedure.
This means that EBCDIC and ASCII will no longer diverge. Currently,
EBCIDIC gives a syntax error for inputs outside its domain, whereas the
ASCII version accepts some of them.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When the replacement is in utf8, there was failure to upgrade the result
when the source and the pattern weren't in utf8. This simply checks
that when there is a match that will lead to the replacement being done.
It then does the upgrade. If this led to changes in the source, we redo
the match because pointers to saved buffers could have changed. There
may be other cases where we don't need to redo the match, but I don't
know the code well-enough to easily figure it out.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Hello,
I have attached a small doc fix for README.aix. It contains information
regarding the new XL C/C++ V11 compiler. This patch is only for bleed.
I have already posted the correct fix for maint-5.12.
Thanks.
Bye
Rainer
From f66807e32b4c01bb58b61cb3e48d89da9c2c4bd7 Mon Sep 17 00:00:00 2001
From: Rainer Tammer <tammer@tammer.net>
Date: Fri, 14 May 2010 09:48:25 +0200
Subject: [PATCH] FIX to README.aix for V11 compiler
Signed-off-by: H.Merijn Brand <h.m.brand@xs4all.nl>
|
|/ / |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* 'blead' of ssh://perl5.git.perl.org/gitroot/perl:
Return 0 (with a warning) for sprintf("%.0g") and sprintf("%.0f")
Updating list of DOSish perls in perlport.pod.
Add Porting/checkpodencoding.pl to MANIFEST
separate the 0755 from the . $TAINT0. this silences the warning "Dot after octal literal is concatenation".
Clarify that mail to perlbug also goes to p5p
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There is special case code in the sprintf implementation, for simple %f and %g
formats, conditionally compiled in only when NVs are doubles. Under long
doubles, these are handled by the general purpose code, which always returns
0 if the argument is missing. Note that sprintf(" %.0g"), ie a leading space,
sufficient to bypass the special case code, would return the string " 0".
The special case code used to return an empty string, meaning that the
behaviour of sprintf("%.0g") and sprintf("%.0f") was inconsistent between a
perl built with doubles, and a perl with long doubles, and the behaviour of
sprintf("%.0g") and sprintf(" %.0g") was inconsistent.
5b98cd54dff3b163 fixed #62874 - the special case code did not warn, but
changed behaviour to return 0. d347ad18ecf3da70 undid the behaviour change,
viewing it as a regression. However, the tests added in 5b98cd54dff3b163
expose the inconsistency in behaviour between doubles and long doubles.
There should be no inconsistency, hence the only logically consistent
conclusion is that the special case implementation was wrong - it cannot
give results inconsistent with the general code. Hence this commit changes
it to return 0 (with a warning). This is achieved by simply skipping the
special case code, if there are insufficient arguments.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
octal literal is concatenation".
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The wording added in 64a8e22bd3 didn't clarify that mail to perlbug is
also forwarded to perl5-porters. Make this section clearer so that it
now explains that perlbug is just perl5-porters + RT tracking.
See the discussion after Craig A. Berry's comment in RT #73914 for
reference.
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The problem is that a dot can come between the braces in \N{foo.bar},
but when searching for it, I didn't stop looking at the right brace, so
it generated an error inappropriately.
This is essentially a minimum patch; efficiency could be improved
slightly with a little more work.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|