Re: Invokes perl modules from perl script in different perl versions

I fail to understand why you don't just re-write everything properly on a current version of Perl (or at least the latest version you've got).

It'd probably be quicker and more resilient, upgrade-friendly and stable long-term as opposed to continuously trying to build and maintain a differing-version abstraction layer.

Comment on Re: Invokes perl modules from perl script in different perl versions

Replies are listed 'Best First'.
Re^2: Invokes perl modules from perl script in different perl versions by maria80e (Novice) on Apr 07, 2020 at 18:22 UTC
Having two versions of a perl is a work around and later we upgrade it into higher version, because its a big project need more efforts.	[reply]
Re^3: Invokes perl modules from perl script in different perl versions by tobyink (Canon) on Apr 07, 2020 at 20:51 UTC
You know, most scripts written for Perl 5.6 will run fine on Perl 5.24 without modification. And you've clearly got Perl 5.24 available. So I don't see why it is a "big project". toby döt ink	[reply]
Re^3: Invokes perl modules from perl script in different perl versions by AnomalousMonk (Archbishop) on Apr 07, 2020 at 22:18 UTC
Like a number of other monks, I don't understand why you don't use version 5.24 of Perl and the necessary TLS interface module and solve the problem without involving Perl 5.6 at all. It would be helpful if you could explain this point. Is it perhaps the case that Perl 5.6 is the system Perl on the server in question and you are unsure about how to install and run a later Perl version? If you avoid the work-around and just do the work, you may find that you have a lot less work to do. See XY Problem. Give a man a fish: `<%-{-{-{-<`	[reply] [d/l]


Keep It Simple, Stupid
	PerlMonks