Several folks have asked me (and I have misplaced their emails) about
whether I had resolved my Devel::Symdump issues because they were
experiencing the same problem. So, with apologies to those several folks,
I am posting here.
Some time ago I posted here when Devel::Symdump failed it's 'make test' and
wouldn't install (modperl is an appropriate list since no symdump means a
modperl make test is skipped).
No one responded, so I did some digging on my own in a territory I had
never before traversed -- which means be EXTREMELY cautious about taking my
conclusions at face value.
The test that failed was #6 in symdump.t. Through a mechanism I have not
yet fully traced out, the test gets a list of all packages and modules that
Devel::Symdump::Export 'uses', including those packages/modules used by the
packages/modules it uses -- in other words (and to untangle the sentence),
a hierarchy.
Test #6 (modules) expects: "Carp Devel::Symdump Devel::Symdump::Export
Exporter strict vars"
Test #6 gets: "Carp Devel::Symdump Devel::Symdump::Export Exporter strict
vars warnings warnings::register"
I fortunately have access to a older system with a 5.005_03 build of perl
to compare my 5.6.0 version against. vars.pm in 5.6.0 includes the
statement "use warnings::register(); while vars.pm in 5.005_03 does not.
I am therefore concluding with CAUTION that the test in Devel::Symdump is
out of date. I updated it in my copy and rebuilt package and installed it.
Time will now tell whether my conclusion was right.
--Rob
_ _ _ _ _ _ _ _ _ _
/\_\_\_\_\ /\_\ /\_\_\_\_\_\
/\/_/_/_/_/ /\/_/ \/_/_/_/_/_/ QUIDQUID LATINE DICTUM SIT,
/\/_/__\/_/ __ /\/_/ /\/_/ PROFUNDUM VIDITUR
/\/_/_/_/_/ /\_\ /\/_/ /\/_/
/\/_/ \/_/ /\/_/_/\/_/ /\/_/ (Whatever is said in Latin
\/_/ \/_/ \/_/_/_/_/ \/_/ appears profound)
Rob Tanner
McMinnville, Oregon
[EMAIL PROTECTED]
