| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Nowhere did it actually describe what cluck does.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've found a bug in File::Spec::VMS->canonpath(), when a dash
component in a directory spec is preceded by a name containing an
escaped period.
My examples show quite clearly where things go wrong:
$ perl -e "use File::Spec::Functions; print canonpath('foo:[bar.coo.kie.--]')"
foo:[bar]
check!
$ perl -e "use File::Spec::Functions; print canonpath('foo:[bar^.coo.kie.--]')"
foo:[bar^.coo.-]
WRONG!
$ perl -e "use File::Spec::Functions; print canonpath('foo:[bar.coo^.kie.--]')"
foo:[bar.coo^.kie.--]
WRONG!
$ perl -e "use File::Spec::Functions; print canonpath('foo:[bar.coo.kie.-]')"
foo:[bar.coo]
check!
$ perl -e "use File::Spec::Functions; print canonpath('foo:[bar^.coo.kie.-]')"
foo:[bar^.coo]
check!
$ perl -e "use File::Spec::Functions; print canonpath('foo:[bar.coo^.kie.-]')"
foo:[bar.coo^.kie.-]
WRONG!
I've created a patch (attached) that solves the issue, with these
correct results (same paths)
[Committer's note: this fixes perl RT #128865]
|
| |
|
|
|
|
|
|
|
| |
This avoids confusing tools like cpanm and carton which use 'provides'
metadata, and are not able to infer the correct data here because
XSLoader_pm.PL is used to generate XSLoader.pm, but then XSLoader.pm is
deleted before cpanm can see it.
|
|
|
|
|
| |
The new version is based on one written by Chris Travers, polished
up a bit by yours truly.
|
|
|
|
|
|
|
| |
As Zefram pointed out in
<https://rt.perl.org/Ticket/Display.html?id=128769#txn-1414015>,
having inconsistent behaviour is going to cause more problems
than solves.
|
|
|
|
|
|
|
|
|
|
|
| |
• Localise @INC only if necessary.
• Don’t mention '.' in the @INC list in the error message, since it
was not in the @INC that was searched (this is accomplished by local-
ising @INC in the same scope as the error).
• If a file exists that would have been loaded had '.' not been
ignored, mention it and suggest ‘use lib’.
• Use the same number of closing as opening parentheses in the
error message.
|
|
|
|
|
| |
I messed up my search and replace and didn't notice it when
committing.
|
|
|
|
|
|
| |
This is my quick-and-dirty script:
find dist -print0 | xargs -0 perl -pi -e 'BEGIN { %map = split " ", join "", `cat pb2rt.txt` } s/(?<!\d)\d{8}\.\d{3}(?!\d)/$& (#$map{$&})/g'
|
| |
|
|
|
|
|
|
| |
I didn't update base.pm since that seems more likely to be loading
modules *expected* to be in the current directory. Opinions
welcome.
|
|
|
|
|
|
|
| |
While currently Encode and Storable are know to attempt to load modules
not included in the core, updates to other modules may lead to those
also attempting to load new modules, so be safe and remove . for those
as well.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
For utf-8 flagged keys the indentation was left as the default, the
key length, and was not updated to the adjusted length after
escaping and quoting.
The test originally used a pre-rendered dump, but potentially other
minor changes to the output would break that, now it simply compares
against the output of the first case.
|
| |
|
|
|
|
| |
with a single warning at import time.
|
|
|
|
|
|
|
|
| |
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829295.
Increment $VERSION throughout ExtUtils-ParseXS/lib.
For RT #128517
|
|
|
|
|
| |
No real changes for blead, but a fixed CPAN distribution with old-perl
backcompat fixes. Thanks to Aaron Crane for the debugging and patches!
|
| |
|
|
|
|
|
|
|
|
| |
Commit 08e3451d made XSLoader confirm that the file path it got
from (caller)[2] was in @INC if it looked like a relative path.
Not taking drive letters into account, it made that @INC search
mandatory on Windows and some other systems. It still worked, but
was slightly slower.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[rt.cpan.org #115808]
The logic in XSLoader for determining the library goes like this:
my $c = () = split(/::/,$caller,-1);
$modlibname =~ s,[\\/][^\\/]+$,, while $c--; # Q&D basename
my $file = "$modlibname/auto/$modpname/$modfname.bundle";
(That last line varies by platform.)
$caller is the calling package. $modlibname is the calling file. It
removes as many path segments from $modlibname as there are segments
in $caller. So if you have Foo/Bar/XS.pm calling XSLoader from the
Foo::Bar package, the $modlibname will end up containing the path in
@INC where XS.pm was found, followed by "/Foo". Usually the fallback
to Dynaloader::bootstrap_inherit, which does an @INC search, makes
things Just Work.
But if our hypothetical Foo/Bar/XS.pm actually calls
XSLoader::load from inside a string eval, then path ends up being
"(eval 1)/auto/Foo/Bar/Bar.bundle".
So if someone creates a directory named ‘(eval 1)’ with a naughty
binary file in it, it will be loaded if a script using Foo::Bar is run
in the parent directory.
This commit makes XSLoader fall back to Dynaloader’s @INC search if
the calling file has a relative path that is not found in @INC.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This reverts commit e6da2a9c4c0cecea6bf21f8ae47d78bdbe8bcbce.
This was hanging parallel testing on my Linux box.
Cause not yest investigated, but revert for now.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[DELTA]
1.9735 [2016-07-21]
- Time::HiRes should override `utime` to allow setting hires
(use futimens and utimensat to implement subsecond utime)
[rt.perl.org #114809]
- the utime patch uses IS_SAFE_PATHNAME() which isn't available in
too old Perls, so emulate (in case the Devel::PPPort is too old)
- make it so that only one value is set for -DTIME_HIRES_STAT
even on systems that support many options
1.9734 [2016-07-17]
- fix Darwins with clock_gettime: blead 2d41a263
[rt.perl.org #128427]
|
| |
|
| |
|
|
|
|
|
|
| |
Not all of the Darwin time code was guarded by the same set of #ifdefs,
leading to bugs on Darwin platforms with clock_gettime where a struct
would not be defined but would still be used elsewhere.
|
|
|
|
|
|
|
|
|
|
| |
As Father Chrysostomos explained on [perl #128319] the previous change
was based on a misunderstanding of the purpose of the test, which is
only to test that constant.pm can create a dualvar out of $! which
has an error string, and nothing specifically to do with E2BIG.
The new comments, also suggested by Father Chrysostomos, make this more
clear.
|
|
|
|
|
| |
Hurd doesn't use 7 for E2BIG, so this string test would fail if the
test itself were more precise.
|
|
|
|
| |
These were found by the new Pod::Checker, soon to be committed.
|
|
|
|
|
| |
The new Pod::Checker soon to be commited doesn't like lines with only
white space.
|
| |
|
|
|
|
| |
For: RT #128197
|
|
|
|
| |
For: RT #128195
|
| |
|
|
|
|
|
| |
I really have no idea what I’m doing. I just copied 4170737e2, sort of,
and the tests started passing.
|
| |
|
|
|
|
|
| |
These modules only ever existed as test data, and should never have entered
the PAUSE index. There is no value in listing them in historical data.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Commit 89988fbd2f7d8a44526a3cd9ab671b3102898bc9 added the relevant phrase for
line-oriented filehandles; this extends that to also cover chunk-oriented
ones.
The patch was supplied by Chris R Donnelly <chris.donnelly@vauto.com> on the
rt.cpan.org ticket; I have extended it to include a test.
|
| |
|