NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Why something would need 5.8.4 (Score:1)
The big 5.8 thing in Perl::MinimumVersion is also "use utf8;". So given the diversity of applications it supports, unicode would seem an obvious one.
Hang on a second.... there's a better way of doing this. perlver to the rescue!
adam@red:~/.cpan/build$ perlver Catalyst-5.33/
-------------------------------------------------------------------------
Re:Why something would need 5.8.4 (Score:2)
Funny you should mention Perl::MinimumVersion, as I would liked to have used it. Its another that is on my list with dependency failures. Unfortunately Test::SubCalls is failing the same tests as imacat's report [perl.org], except mine fails on Windows, Perl 5.6.1.
I have been doing the checking by hand previously and noting to the authors that it really does work for 5.6.1, however I had planned to write something that can do that (using Perl::MinimumVersion) to check a distribution as soon as it produces a NA repor
Re:Why something would need 5.8.4 (Score:1)
Reply to This
Parent
Re:Why something would need 5.8.4 (Score:2)
That should perhaps feature a bit more prominently in their docs I think.
However, I was only cpan-testing Catalyst and related modules, so manual intervention wasn't the plan. It just means I don't test anything Catalyst dependent anymore.
Reading the fix, I'm more inclined to get frustrated that there isn't an independent release for some core modules, so that those of us who can't upgrade past 5.6.1 can still get the benefit of fixes. If these fixes to Class::Struct work fine on 5.6.1, why is there a de