At first glance this is a crazy question -- just test it out. If you look again it is really a question that asks -- how do I verify that my use of an external dependency will continue to work across versions? Now, that is not a silly question at all.
'Just test it out' is correct, but the how is the important part. If you have a critical script then it should be worth your time to modularize most of its operation and write tests. Add tests that specifically target the parts of those external modules that your script is relying on. For instance, Text::CSV has a fields() method that according to the pod will return an undefined value under certain circumstances. Then, when you want to validate that a newly released module will work, you can run it in an environment that uses the new version of the module and execute those tests. Learn to use Test::More, etc.
Celebrate Intellectual Diversity
| [reply]
[d/l] |
| [reply] |
Just test it. ;-) And possibly also read the documentation which might give some clues. No other way around. Or, at least, we can't say more, especially when we have no idea whatsoever about what your script does and which module you are talking about. Most of the time, module authors will try to keep the interface valid and to keep the existing functionalities (and possibly adding new ones), so that that a new version of the module should work at least the same way as the older ones, but this is far from being guaranteed for a number of reasons (need to improve a faulty the interface, dependencies on other modules, etc.).
| [reply] |
You just posted an exact dupe of this question twice, as 1087794 and 1087796. Just in case you weren't aware, new questions don't appear on the front page immediately, you can check Newest Nodes or Recently Active Threads instead. You should be able to find the links at the top right of the page.
| [reply] |