comment on

If requirements don't dictate a version of Perl to target, what version do you target when writing code for reuse?

I generally target 5.6. It is probably the most widely installed perl these days and I have never been in a situation (yet) where I absolutely needed a 5.8 feature. Indeed, I don't know that I've ever absolutely needed a 5.6 feature, but things like lexical filehandles, our instead of use vars, etc. are rather convenient.

Put differently, what features are you willing to give up for backwards compatible code?

I'm not willing to give up much beyond Perl 5.6. IMHO, 5.6 is really the time when Perl 5 became a mature, "stable" programming language. 5.8 is a great accomplishment but it's not as big a milestone was 5.6 was.

In reply to Re: Writing for backwards compatibility by friedo
in thread Writing for backwards compatibility by xdg

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.


Syntactic Confectionery Delight
	PerlMonks