Personally, I like to write multiple modules that all implement the same API, like the following:
package Super::Cool::Perl5_006;
# The most basic implementation
package Super::Cool::Perl5_008;
use Super::Cool::Perl5_006; # First import all the stuff from 5_006
# and overwrite some of the newer stuff
package Super::Cool::Perl5_010;
use Super::Cool::Perl5_008;
# Not totally basic implementation
The package Super::Cool then basically loads the appropriate implementation package and exports the subroutines into the calling package.
This approach is great until you have a longer subroutine which has a common setup case and then one (or more) special cases after the common setup. My approach would then move the special handling into a separate subroutine, which makes the code more disjointed as the logic is then spread out over more subroutines. The alternative would be to copy and rewrite the subroutine for each Perl version, which carries its own hazards.
-
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.
|