| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
(cherry picked from commit 15a348aa1f233f84aedc3c0a7bcc9d29fc6dc9e9)
|
|
|
|
| |
(cherry picked from commit dee33c9459543bbd59d00c5418b9b2183239205d)
|
|
|
|
| |
(cherry picked from commit 21863e7e0890fa3f55e9efd85a0746d312e7dc53)
|
|
|
|
|
|
|
|
|
|
|
|
| |
things, but does not address the "this version" != 5.14 and the
perlio issues. I believe that these at least should be addressed
as soon as possible (I don't know whether that means 5.14;
probably not). It has to either say the particular version that
applies. We can't keep releasing things that say this version:
they are not trustable.
--tom
(cherry picked from commit f4750dabedb3961d2aa3fec0bc3a92de1ebc06b6)
|
|
|
|
| |
(cherry picked from commit 530f0126691388f9891b28f639f47e4280836ccc)
|
| |
|
|
|
|
|
|
| |
In addition to documenting the recent integrations, I also
removed the ‘Selected’ from the ‘Selected Bug Fixes’ title,
as maint perldeltas should list *all* bug fixes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Formats are compiled down to a sequence of U32 opcodes in doparseform().
Previously the block of opcodes was stored in the buffer of SvPVX() after
the raw string by extending the buffer, and calculating the first U32 aligned
address after SvCUR(). A flag bit on the scalar was set to signal this hackery,
tested with SvCOMPILED()
The flag bit used happened to be the same as one of the two used by to signal
Boyer-Moore compiled scalars. The assumption was that no scalar can be used for
both. Unfortunately, this isn't quite true.
Given that the scalar is alway upgraded to PVMG to add PERL_MAGIC_fm magic,
to clear the cached compiled version, there's no extra memory cost in using
mg_ptr in the MAGIC struct to point directly to the block of U32 opcodes. The
test for "is there a compiled version" can switch to mg_find(..., PERL_MAGIC_fm)
returning a pointer, and the use of a flag bit abolished.
Retain SvCOMPILED() and SvCOMPILED_{on,off}() as compatibility for XS code on
CPAN - the first is always 0, the other two now no-ops.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I also fixed a bug in the original. I'm always getting C<eof> vs C<eof()>
swapped in my brain, which is what had happened here. The old code didn't
do what it said it did because it contrary to the comments didn't reset at
each eof -- because it used the C<eof()> form which is all of ARGV rather
than bare C<eof> for the last file read, and thus each per-file component
of ARGV.
I am concerned about the two paragraphs previous to that, because they
use eof() and I am not perfectly clear that they should. But I left
them as is.
Jesse asked for "a lot of eyes", so if folks could please look at this
patch and see whether it looks ok, I'd appreciate it. I did test it
under blead, both with and without the prefixed m on the m?? matches,
which is how I discovered it was buggy with the C<eof()> not C<eof>.
--tom
|
|
|
|
| |
somewhere other than perldelta.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
• Remove C<...> around get-magic and set-magic. Those are prose
descriptions of what is known internally as mg_get, SvGETMAGIC,
SVs_GMG, etc.
• Re-instate the message that 804b5feed removed, but in the form in
which it appears in perldiag.
• Remove the thing about version class methods. It’s a bug fix, not a
problem (whether known or unknown :-), and not a significant one.
• Spelling mistake
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Apparently the writers of perldiag realized that "%s%s" is the same
as %s for the purposes of diagnostics, so there is no anchor for the
removed link.
|
| |
|
| |
|
|
|
|
| |
Also the possibility of an undefined initial locale
|
|
|
|
|
| |
C<foo"bar"> will translate into "foo"bar"" on some devices, which is
confusing. Change the remaining ones to C<foo'bar'>
|
| |
|
|
|
|
| |
I've verified as fixed.
|
| |
|
|
|
|
| |
statements as C<function()>
|
|
|
|
|
|
|
|
|
|
| |
cryptographically secure due to concerns that end-users are unaware of
this and use it in situations where security depends on the strength of
the randomness generated.
I'd have been happier getting this patch in earlier in the cycle.
We'd hoped to replace the RNG, but that didn't happen in time, so this
doc update is the "better, still not good" fallback.
|
| |
|
| |
|
| |
|
|
|
|
| |
Test::Harness 3.23
|
|
|
|
| |
I've pod-, spell-, and dupword-checked this.
|
|
|
|
|
| |
• Mark it as experimental
• Remove paragraphs that no longer apply
|
| |
|
| |
|
|
|
|
|
|
| |
This pod misled some people, including this author, as to the initial
state of locales. This fleshes out some details, and changes some
wording.
|
| |
|
| |
|
| |
|
| |
|
| |
|