I suffered for it, but after some unsatisfying experiments I accepted following philosophy, assuming both versions of the module exists in some concurrent version system:
If it is not absolutely necessary to use both versions in the same process, just put proper versions to special paths, dedicated for this purpose. Then you can have two or more paths for two or more versions and you can run one process for every version and compare their behavior, having remaining parts of the program identical.
If it is absolutely necessary, rename versions (MyModule0_71.pm) for testing purposes. Though it is ugly work, it consumes less time than fiddling Perl guts, and it does not make chance that fiddled solution will work differently from renamed solution.
-
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.
|