People like you are the reason why I keep trying very very hard to have my CPAN modules support old(er) versions.

I am really very sorry to tell that I had to drop 5.005 support, but I now ran into problems that needed 5.6 or up. Some of my (perl) friends cheered in my decision to drop 5.005, but until I did, the burden to support it was low. Now that I dropped it, a lot of stuff got easier and I somehow regret not dropping it earlier.

I still have over 100 versions of perl available on my USB testing disk, and I notice that it is getting harder by the day to support 5.60 and 5.6.1 as the required toolchain just won't install anymore, so I'm actually stuck with 5.6.2 or newer for a lot of recent development. At least it proves that perl's own development hasn't stalled. Most failures for 5.6.1 and older stem to compilers that are newer than what those perl versions support or library mismatches between when those perls were built and what the system currently offers. Well, there is no easy workaround to that.

In my job I have the relative luxury that I have been able to convince the clients to not use system perl (on HP-UX and AIX) as they do not reliably support 64bitnes and/or Unicode, two major requirements for most perl processes run in customer environment. Now we - as 3rd party - can decide what perl version we install on the client side next to the system perl (which isn't used at all by our applications).