Re^3: New error message in ActivePerl 5.22

Can't help with ActivePerl (but their page mentions 5.10 as supported in their enterprise edition). I'd go for StrawberryPerl; on their releases page they have 5.10.1.5 (May 2011). The ZIP edition (as opposed to the MSI installer) doesn't need admin privileges and therefore will not mess with the system's internals, which is why i prefer this method.

Then there is berrybrew, which allows you to use multiple (Strawberry) Perl versions concurrently, so you could first get your scripts to work again using 5.10 and later switch to a newer Perl (and back and forth).

Comment on Re^3: New error message in ActivePerl 5.22

Replies are listed 'Best First'.
Re^4: New error message in ActivePerl 5.22 by dhannotte (Acolyte) on Dec 29, 2017 at 17:39 UTC
Thanks for your great advice, soonix. I'm now working on installing, understanding and exploiting Strawberry. Since I don't get around much anymore I thought I'd just install the .MSI version of 5.10 but the installer issued the message "Installer is no longer responding" for an hour, so I had to give up. (I'll report this to them as soon as I have time to figure out their complicated reporting procedures.) So far I'm getting the same results whether I issue programname.pl or c:\perl programname.pl. In either case $] is set to 5.22, the version I'm trying to avoid. Is there any way my program can sense that it is running Strawberry Perl rather than ActiveState Perl?	[reply]
Re^5: New error message in ActivePerl 5.22 by soonix (Chancellor) on Dec 29, 2017 at 22:05 UTC
I use the "Portable editions". I see on the http://strawberryperl.com/releases.html page several 5.10 versions, some with and some without. The "portable" ones (e.g. Version 5.10.1.2) can be extracted to an arbitrary folder. There will be a "portableshell" Batch or CMD file which will give you a command prompt. As long as you call it from inside that special command prompt, it will find its own Perl version, even if you have several of them lying around. The ZIP edition seems to have the restriction that it must be extracted to C:\Strawberry, and you have to add it to the PATH manually. In all cases, modules have to be installed for each of these versions separately (if you use multiple versions) That said, you should look over your environment variables, anyway, because many installers add their software to the PATH, and let it there upon uninstallation, so that it might grow beyond its limit. This might cause errors similiar to the one you described.	[reply]
Re^4: New error message in ActivePerl 5.22 by Anonymous Monk on Dec 25, 2017 at 20:44 UTC
Do you actually use berrybrew?	[reply]
Re^5: New error message in ActivePerl 5.22 by soonix (Chancellor) on Dec 26, 2017 at 18:51 UTC
Not currently. I did try it out for curiosity's sake and to test if it works as advertised. But I'm already used to my setup with ConEmu with half a handful of Perls which I need to use both with and without admin privileges.	[reply]