| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Core-only modules that have changed from v5.13.7, and dual-life modules
that have changed from v5.13.7 and didn't show up in earlier passes.
|
|
|
|
|
|
|
|
|
|
|
| |
Trivial changes to fix warnings of types
* unclear precedence
* assignment as conditional
* signed/unsigned mixing
* unused parameter/variable
* value computed not used
* wrong argument type for a printf format
* variable may be used uninitialised (due to unhandled switch case)
|
| |
|
| |
|
|
|
|
|
|
|
| |
$ perl5.10.1 -le 'print *{*STDERR{IO}}'
Bus error
That crash is beyond DD’s control, so the test should be skipped.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
When warnings are enabled and Dumper() is called with an invalid utf8
string that still has the UTF8 flag on, esc_q_utf8() miscounts the size
of the escaped string.
|
|
|
|
| |
just in case 5.13.6 is released before the next CPAN release of DD.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Bus error
Same in 5.11.4.
This is related to bug 71254. It turns out that globs *can* stringify
emptily (see bug 65582). This patch makes DD more resilient.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds (?^...) to signify to use the default regex modifiers for the
cluster or embedded pattern-match modifier change. The major purpose of
this is to simplify regex stringification, so that "^" is output in
place of "-xism". As a result, the stringification will not change in
the future when new regex modifiers are added, so tests, etc. that rely
on a particular stringification will have to change now, but never
again.
Code that needs to work properly with both old- and new-style regexes
can use something like the following:
# Accept both old and new-style stringification
my $modifiers = (qr/foobar/ =~ /\Q(?^/) ? '^' : '-xism';
This construct is Ben Morrow's idea.
|
| |
|
| |
|
|
|
|
|
| |
Based on work by Father Chrysostomos <sprout@cpan.org>, but all
my fault.
|
|
|
|
| |
No significant changes, just synchronization to the exact release.
|
|
|
|
|
| |
RT #73604: When $Data::Dumper::Terse is true, the indentation is thrown
off. It appears to be acting as if the $VAR1 = is still there.
|
|
|