| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Full commit message to come later....
|
| |
|
|
|
|
| |
This test doesn’t care what glob actually does in this case, but
merely how many times it calls magic. So suppress any warnings, in
order for tests to pass on VMS.
|
| |
|
|
|
|
| |
Prior to the preceding commit, the ‘glob failed’ warning would always
occur, regardless of warnings settings, so W was never correct. Now
it is S, which is was it used to be closest to.
|
| |
|
|
|
|
|
| |
The ‘glob failed’ warning was not respecting warnings settings. The
warning used to occur even under ‘no warnings’. This commit makes it
a severe warning. I.e., there is no change when warnings are con-
trolled by $^W and $^W is 0, but only under ‘no warnings 'glob'’.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
It was already documented that when scanning for the end of the string,
backslashes escaping the closing delimiter are being eliminated; but
this is true for backslashes escaping backslashes as well. This makes
that C<< '.\.' eq '.\\.' >>. (Pointed out by Mithaldu)
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
commit 5bec93bead1c10563a402404de095bbdf398790f made temporary use of the
no-longer used SvMAGIC field while freeing a HV. This commit makes
sure that before this happens, that the SvMAGICAL flags are turned off.
This is because it turns out that some XS code (e.g. Glib) can leave an SV
with a null SvMAGIC field, but with magic flags still set.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Two commits ago, the label-handling code in the tokenizer was changed
to record the label in an SVOP instead of just a plain unclaimed PV.
Likewise, the parser (perly.y) was changed to copy the string out of
the SVOP’s SV, insteading of taking ownership of the existing PV.
parse_label was modified to take the string out of the SVOP, but was
not copying it like perly.y. So it resulted in this:
$ PERL_DESTRUCT_LEVEL=2 ./perl -Ilib ext/XS-APItest/t/swaplabel.t
1..56
ok 1
... truncated ...
ok 56
panic: free from wrong pool during global destruction.
|
| | |
| |
| |
| |
| |
| |
| | |
This fixes up tests added in the previous commit, making them take
evalbytes into account. Those tests were originally written in a
branch where evalbytes didn’t exist and the unicode_eval feature
was implicitly enabled.
|
| | |
| |
| |
| |
| | |
This meant changing LABEL's definition in perly.y, so most of this
commit is actually from the regened files.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
These are more of Brian Fraser’s UTF8 patches from perl
ticket #107008.
There will probably be just one more before 5.16 (the label patch).
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ / |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When the record read feature was introduced in 5b2b9c687790241e8
in 1998 (but by Dan Sugalski, not Hans Mulder as the git history
erroneously says), sysread() was a couple of years from learning
about utf-8 and PerlIO was just a fancy way of calling stdio. The
documentation was reasonable given that environment.
Now it's potentially misleading to say that record reads are "the
equivalent of C<sysread>" because sysread on filehandles opened
with ":utf8" does characters, not bytes. The salient point about
the analogy with sysread was always that the read is unbuffered.
In the old days, this was in contrast to the buffering done in
stdio's fread(), but now it's in contrast to the buffering in the
perlio layer. By emphasizing the role of buffering, we can
actually shorten and simplify the docs.
Side note: Both Camel 3 and Camel 4 have the following problematic
statement in the documentation of $/: "Record mode mixes with line
mode only on systems where standard I/O supplies a read(3) function;
VMS is a notable exception." VMS certainly does have a read(3)
function and in fact that's what's used directly for record reads
(via PerlLIO_read) on VMS only. And as far as I know, it is
fread(), not read(), that is considered "standard I/O" everywhere.
N.B. Record reads on non-record-oriented files on VMS will likely
start using the same buffering as other platforms in a future
version of Perl.
|
| | |
| |
| |
| |
| |
| | |
The previous patch was written before HEKf existed.
HEKf with HEKfARG(...) is much faster than SVf with
SVfARG(sv_2mortal(newSVhek(...)))
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Outdent code that previously was enclosed in a block
|
| |/
|
|
|
| |
This refactors to test for the hash element being defined before
attempting to use it.
|
| |
|
|
|
|
| |
It's kind of late in the release process to change how $/ = \N works
for unicode streams, briefly document how broken it is and let the
user know it may change.
|
| |\
| |
| |
| |
| |
| |
| |
| | |
This branch represents more of Brian Fraser’s patches from
<https://github.com/Hugmeir/gsoc-pad-utf8-safety/commits/tokemess>,
that are referenced by perl #107008.
This is not all of it, but all I’ve merged and tested so far.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
This was added in the previous commit, but was unnecessary, as it
is not used anywhere and is not part of the public API.
|
| |/ |
|
| | |
|
| |
|
|
|
| |
Also, indent the epigraph of Perl 5.15.9, to prevent the text to be
formatted.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
