Your skill will accomplish
what the force of many cannot
Benefits/Disadvantages of version Object/version.pmby jawnsy (Novice)
|on Jan 31, 2009 at 21:44 UTC||Need Help??|
jawnsy has asked for the
wisdom of the Perl Monks concerning the following question:
Hello wise Monks:
I develop modules for CPAN. Generally, I see modules that are included in the Core of the perl distribution to be the "preferred" modules when solving a particular problem. So naturally, when I discovered version.pm, I started using version objects/qv() in my code.
This is a question I've searched for, on Google, on PerlMonks, but so far I have turned up nothing substantive.
Today I was discussing with mst@freenode#perl the benefits and disadvantages of version.pm. I myself use it "just because" it seems like the "generally accepted" thing to do - seeing as how it's a core module. Perhaps this is the wrong way to think. It might be an important module to use, but the reasoning behind it isn't as obvious as "use warnings" or "use strict."
So, I ask you all, as a CPAN developer (ie, where there are many modules that may interact with each other in unpredictable ways), do the benefits of version.pm outweigh any reasons against its use? In general, should CPAN developers version their modules this way?