Stas Bekman wrote:
May be you are right, Hugo, in which case perl provides no function to figure a version number without first loading the module. Besides, no module that ever wants to run under -T environment can use ExtUtils::MM_Unix->parse_version, because it will break. If you have an alternative solution, please suggest it.
If you don't mind the extra dependency, it should be possible to add this to the CPAN "version" module (and thence to the core in 5.9.x). I just need a name for the new function (I don't like parse_version that much).
That makes sense, John. I'm not sure what's the best name. no_load_parse_version? module2version?
As a side note ExtUtils::MM's functions should have never left the scope of EU::MM internals. e.g. people suggest to use ExtUtils::MakeMaker::find_perl because it's the only function shipped in the core that gives you more or less correct path to perl, but no one cares that it loads heaps of modules and runs tons of code to achieve a simple goal that perl core should have provided the method for in first place (i.e. $X is not suitable for running an external process on many platforms, nor $Config{perlpath} ).
Besides, If you are going to say:
require Foo;
doesn't it make Foo trusted enough to make contents of Foo.pm trusted for eval STRING?
That seems reasonable...
I thought so ;)
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
