-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DB::files() and DB::loadfile() failing to locate files #195
Comments
When using
|
What do you get if you say:
... where I assume that Thank you very much. |
yes it's the file above, I should have removed its name from the output and forgot about it...
I left the file in the root directory and adjusted the inc setup |
The problem described in this ticket is not of our doing. The file passes with 3 skips in one case and passes with those 3 tests run in the other. So this is not something we have to worry about or can do anything about. Closing. Thank you very much. |
Consider the following file, which is adapted from
lib/DB.t
in the Perl core distribution:The file essentially consists of 4 blocks from the original file, hacked up with debugging code and one Data::Dumper call. Our focus will be on blocks 2 and 4.
If we place this inside the Perl 5 core distribution and run it, we get this output:
If, however, we run this against Perl 7 -- I'll temporarily included it in the distribution in the
alpha-dev-02-strict
branch -- we get different output.Note that in Perl 7 we're not picking up the
.pm
files we are in Perl 5 atAAA
in Block 2. We're not picking up any files atBBB
.CCC
suggests we're failing to find 68 files that we would find in blead.And because in Block 4 we're not picking up any files at
YYY
, the test isskip
ping the last 3 tests rather than running them against properly located files.At this point in the branch's development, there have been no changes yet in
lib/DB.pm
.And the only change in
lib/dumpvar.pl
that I've made is to insert an explicitno strict;
(cf. #193).So I suspect the problem lies in other code I've touched or mangled, perhaps in
ext/B
or `lib/B'.Note: As it stands in the branch,
lib/DB.t
is not strict-compliant. When I went through it to insertno strict 'refs'
and similar statements in an attempt to get it to be strict-compliant, I came to a point where I had to insert a relaxation of strictures into one part oflib/DB.pm
. When I then ranlib/DB.t
, it froze my system and I had to do a hard reboot. Hence, inlib/DB-small.t
, I've removed all code below the relevant blocks, because the places wherelib/DB.t
were not strict-compliant all fell below those blocks.@atoomic @toddr
Thank you very much.
Jim Keenan
The text was updated successfully, but these errors were encountered: