Clear questions and runnable code get the best and fastest answer |
|
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Personally, I think the correct answer is: Don't! Someone set up a 5.6 server 10 years ago and installed v1.x of XYZ that was available then, and it worked for them. A few years later someone (maybe the same someone) sets up a 5.8 server and installs v2.x of XYZ and it works for them. A few years on and someone (...) sets up a 5.14 server with version 3.x of XYZ and it works for them. You are writing version 4.0 of XYZ, and adding new features. Are you anticipating that the guys still running Perl v5.6 is going to replace his working installed version of XYZ with your latest code? Why would he do that? To make use of the new features, he would have to modify his code to use them. But this is a man still running a perl 5.6! It just doesn't seem likely he is going to modify anything. His existing code works; his installed XYZ v1.x still works. Why would he change? Ditto the others. The only reason I can see for doing what you're asking, would be if you've received a bug report for (say) the 1.x version and your intent is that the fix is to tell the guy to upgrade. Good luck with that :) With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)
In the absence of evidence, opinion is indistinguishable from prejudice. Not understood.
In reply to Re: The "right" way to make your script run with old versions of perl (why?)
by BrowserUk
|
|