| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 50e5165b9638b94be310f15477b42935c79e82d5.
That commit fixed the leak too well and instead introduced a potential
premature free.
This re-introduces the long-standing leak, which will be addressed post
5.22 release.
See RT #124181
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
cde405a6b9b86bd8110f63531b42d89590a4c56e removed the lock prototype
"because it's already a do-nothing weak keyword without threads".
However, that causes "perl -d threaded-script.pl" to complain
lock can only be used on shared values at /usr/share/perl/5.20/perl5db.pl line 4101.
BEGIN failed--compilation aborted at threaded-script.pl line 2.
lock can only be used on shared values at /usr/share/perl/5.20/perl5db.pl line 2514.
END failed--call queue aborted at threaded-script.pl line 2.
Unbalanced scopes: 3 more ENTERs than LEAVEs
because threaded-script.pl's importing of threads::shared enable's
lock()'s non-noop behavior. Restoring the lock() prototype fixes the
inconsistency between lock() and share() usage.
Signed-off-by: James McCoy <vega.james@gmail.com>
|
|
|
|
|
|
|
| |
"The $ENV{...}," doesn't read well;
Spell it out for consistency with perlrun.
Committer: Increment $VERSION and add entry to perldelta.
|
|
|
|
|
|
|
|
|
|
|
| |
The targlex optimisation (which makes the op write directly to the
lexical in $lexical = some op, skipping the assignment) does not take
typeglob assignment into account. Since this optimisation has been
enabled for some ops in 5.21.x, we actually have a regression. So
this commit disables the optimisation once more for ops that did not
have it on in 5.20. This is a temporary fix, until we find a better
overall fix. Other ops that still have the optimisation are buggy,
but no more buggy than in 5.20.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After additional discussions on perl5-porters and #p5p, no one seems to
be violently objecting to the idea that FATAL warnings need a much
stronger warning about risks and that FATAL => 'all' should actually be
'discouraged' in the official, perlpolicy sense.
The text of this commit has been posted to perl5-porters for discussion
and approved by those who objected to earlier language.
I dare not call it "consensus" for fear of the consequences, but no one
has raised further obstacles to making this change.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
An empty cpan/.dir-locals.el stops Emacs using the core defaults for
code imported from CPAN.
Committer's work:
To keep t/porting/cmp_version.t and t/porting/utils.t happy, $VERSION needed
to be incremented in many files, including throughout dist/PathTools.
perldelta entry for module updates.
Add two Emacs control files to MANIFEST; re-sort MANIFEST.
For: RT #124119.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
I tried to make the necessary changes for Perl v5.22 to work with old
Unicode versions, but ran out of time before the code freeze, with 5.1
being the earliest version. The sticking point there is that the
Capital Sharp S, U+1E9E, was defined in that release. Because of its
anomalous behavior with the infamous lower case sharp s, U+00DF, there
is a bunch of hard-coded references to it in the C code which need to be
adjusted to handle it's absence.
|
| |
|
|
|
|
|
|
|
|
| |
Unicode adds new files to its character database from time to time in
new versions of the Standard. mktables is supposed to be able to handle
this when it knows about a file, but it is compiling a version of the
Standard that predates that file's existence. It was not dealing
properly with this situation.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Several /lib .pm's have the same code which is complicated enough to
warrant being placed in a shared function. This commit creates a .pm
to be used by these .pm's.
This implements the perhaps archaic 'Meta' notation wherein characters
above 0x7f are displayed as M- plus the ASCII-range character derived by
looking at only the lower 7 bits of the upper range one. There are
problems with this, in that a literal control character can be in the
string, whereas it is trying to get rid of control characters. But I
left it to work as-is, just centralizing the code.
On EBCDIC platforms this notation makes no sense because the bit
patterns are all mixed up about having the upper bit set. So this
commit fixes things on these platforms, so these are changed to
\x{...}. No literal control characters are emitted.
Another potential problem is that characters above 0xFF are passed
through, unchanged. But again, I let the existing behavior stand.
|
| |
|
| |
|
|
|
|
|
|
|
| |
...at least for now.
This reverts commits 0d314ba30623b19c36dfc97ac4b6ecb94cb406f4
and ce3778a3796be3e4604ed9b3671ea624c5affe0b.
|
|
|
|
| |
Slight grammatical touch-up to cautions against FATAL warnings.
|
|
|
|
|
|
|
|
|
|
|
| |
Discussions on p5p have reached reasonable consensus that fatal warnings are
a misfeature.
This commit marks fatal warning as "discouraged" and moves up the
related cautionary documentation to highlight the risks of using them.
For details on the many historical and current issues with fatal warning, see
http://www.nntp.perl.org/group/perl.perl5.porters/2015/01/msg225235.html
|
| |
|
|
|
|
|
| |
This still has a failure due to Encode issues. A future commit will
skip some failing tests until that is fixed.
|
|
|
|
|
|
|
|
| |
This involved changing a \xff to \xfe because it is expecting it to be a
character whose representation is different when encoded in UTF-8, and
on some EBCDIC platforms, \xff is UTF-8 invariant. I suppose there
could be a code page where \xfe is invariant, so this .t would have to
be made more general if that ever comes to be.
|
|
|
|
|
|
|
| |
These just return their argument on ASCII platforms, so can get rid of
the function call overhead there.
Thanks to Zefram and Matthew Horsfall for their help in this.
|
|
|
|
|
| |
This worked for EBCDIC 1047, but not for other pages. This commit
changes to use the tools created for the purpose to make it general.
|
|
|
|
| |
This pod is generated by mktables.
|
|
|
|
| |
Indent inside new block formed in the previous commit.
|
|
|
|
|
|
|
| |
It is possible to compile Perl without locales, and some platforms may
not have them available properly. These tests were failing under these
conditions. This commit uses the new infrastructure in loc_tools.pl to
centralize the knowledge of how to determine if locales are available.
|
| |
|
|
|
|
|
| |
This includes choosing a different code point that has 3 bytes in both
UTF-8 and UTF-EBCDIC, so that the pos numbers work for both.
|
| |
|
| |
|
|
|
|
| |
Properly indent within a block
|
| |
|
|
|
|
| |
These were broken by the upgrade of Unicode::UCD to version 0.61
|
| |
|
|
|
|
|
|
|
|
|
| |
8c2e27d changed B::Deparse to deparse $#{1} as that instead of as $#1
which is a syntax error, but also changed $#_ to deparse as $#{_}
which isn't necessary, and broke GFUJI/macro-0.06.tar.gz
This could be considered a bug in macro.pm, but since we don't need to
deparse $#_ as $#{_} let's not do that.
|
|
|
|
|
|
|
|
| |
// in the scope of lexical $_ gets the OPpTARGET_MY flag set. If it
is used as an operand to smartmatch, it gets converted to a qr op.
There is no need to turn off the flag, since it is harmless at run
time. But we need to allow the flag on this op type to avoid asser-
tion failures when it is freed.
|
|
|
|
|
|
|
|
|
|
|
|
| |
This case fails an assertion:
my($_);0=split
because a pushre op is not expected to have that flag. A pushre op
starts out as a match op (which may indeed have the flag set), as is
subsequently converted to a pushre op.
[The commit message was written by the committer.]
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The lib/h2ph.t test executes a t/lib/h2ph.pht which requires
'_h2ph_pre.ph'. This should find and exercise generated t/_h2ph_pre.ph
file. However, it found a loaded _h2ph_pre.ph from system because the
interpreter has the './' directory after the system paths in the @INC by
default.
This patch adds '-I./' to the runperl() invocation to prefer the
_h2ph_pre.ph generated at build time.
Signed-off-by: Petr Písař <ppisar@redhat.com>
|
| |
|
| |
|
| |
|