| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: David Golden <dagolden@cpan.org>
|
|
|
|
|
|
| |
Test-Harness RT #59186 and RT #59457 introduced some
regressions. These are being fixed upstream but didn't make it into
this release.
|
| |
|
|
|
|
|
| |
"Improved documentation of unusual character escapes" was fixed up in
9644846.
|
|
|
|
|
|
| |
"Improved documentation of unusual character escapes (bf82ca4)" added
in a0316a43 should have referenced 4068718. There's no bf82ca4 commit
in the perl repository.
|
| |
|
|
|
|
|
| |
Include the explanation from my cae9400 patch in the perldelta so that
it can be understood when read stand-alone.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Mention that C<eval sprintf "%#X", 0x10> now works, and that upper
case hex/binary literals are supported in C and friends.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This patch adds a mention of \o{} to perlre to avoid the backreference
ambiguities, and uses 3 octal digits in an example, and suggests using 3
digits where 2 were suggested before.
Signed-off-by: David Golden <dagolden@cpan.org>
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Some dual-life modules have custom files in core that differ from
CPAN. (e.g. Makefile.PL in libnet) These files need to be listed
in EXCLUDED, but also in CUSTOMIZED so that we don't flag them
incorrectly as "only in Perl"
|
| |
|
|
|
|
|
|
| |
Because we manually generate Makefiles, any executables need to be
generated from .PL files in utils/. This test checks if dual-life
executables show up in utils/.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Extracted directories are cached and re-used
* Perl vs CPAN version mismatches shown in summary output
* Various minor code cleanup
Some diagnostic output was surpressed in diff mode, but not all.
I found the output confusing to follow in diff mode as a result
so I enabled some of the previously surpressed output.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Now that CvGV can sometimes be reference counted, stop people from directly
assigning to it (by using CvGV as an lvalue), and instead force them to use
CvGV_set()
|
|
|
|
|
|
|
|
|
|
|
| |
Rather than making CvGV refcounted if the CV is anon, decide based on
whether the GV pointed to by CvGV holds a reference back to us. Normally
these two will be equivalent, but this way is more robust if people are
doing weird things.
Also spotted an error with cv_clone not clearing the CVf_CVGV_RC flag on
the newly cloned cv. This shouldn't normally matter as it will get set
shortly anyway, but best to keep things logically correct.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
after the recent commit 803f274831f937654d48f8cf0468521cbf8f5dff,
the CvGV field is sometimes reference counted. Since it was intended that
the reference counting would happen only for anonymous CVs, the CVf_ANON
flag was co-opted to indicate whether RC was being used. This is not
entirely robust; for example, sub __ANON__ {} is a non-anon sub which
points to the same GV used by anon subs, which while itself doesn't
directly break things, shows that the potential for breakage is there.
So add a separate flag just to indicate the reference count status of the
CvGV field.
|
| |
|
|
|
|
| |
This is a merge resolution based on original work by Karl Williamson.
|
|
|
|
|
|
|
|
|
|
| |
This commit adds the new construct \o{} to express a character constant
by its octal ordinal value, along with ancillary tests and
documentation.
A function to handle this is added to util.c, and it is called from the
3 parsing places it could occur. The function is a candidate for
in-lining, though I doubt that it will ever be used frequently.
|
|
|
|
| |
Signed-off-by: David Golden <dagolden@cpan.org>
|
|
|
|
| |
Signed-off-by: David Golden <dagolden@cpan.org>
|
|
|
|
| |
Signed-off-by: David Golden <dagolden@cpan.org>
|
|
|
|
| |
Signed-off-by: David Golden <dagolden@cpan.org>
|
|
|
|
| |
Signed-off-by: David Golden <dagolden@cpan.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Prior to this patch, \400 - \777 meant something different in some
circumstances in regexes outside bracketed character classes. A
deprecated warning message has been in place since 5.10.1 when this
happens. Remove the warning, and bring the behavior into line with the
other double-quotish contexts. \400 - \777 now always means the same
thing as \x{100} - \x{1FF} (except when the octal forms are taken as
backreferences.)
Signed-off-by: David Golden <dagolden@cpan.org>
|
|
|
|
|
|
| |
These come from Abigail.
Signed-off-by: David Golden <dagolden@cpan.org>
|
|
|
|
|
|
|
|
| |
My vim settings were causing extra blanks in this file; remove the ones
I added recently and set the vim options to disable the offending
feature.
Signed-off-by: David Golden <dagolden@cpan.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Which was clobbered by 7b0eef92ba8ed2aa84e9187dadebc5cabfc3a3c5.
And still awaiting upstream integration at:
<https://rt.cpan.org/Public/Bug/Display.html?id=55236>
Also bumped the version this time to leave a better clue that something
has changed in blead.
|