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
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
