One of these days you lot are going to learn that sometimes the simplest answer is infact the best, that all these high-faluting technical wizardry incantations do nothing but slow Perl down by trying to make it be something that it was never intended to be, nor will it ever be.

Object orientation is programmer masturbation, a passing fad, and truly a bad idea that really does make programmers blind.

I pity you lot. I really do, the lengths you will go to try and force Perl be something other than Perl.... Why? Because after years of jacking off about how wonderful object orientation is, you've completely and utterly missed the point of Perl, to such a degree that your planning to kill off older versions which work perfectly well on millions of servers in your pursuit of a technological pipe-dream of elegance.

And what do you get? Yet another computer linguistic straight jacket like JAVA which does nothing but tie you and the lady Perl up in knots and decimate performance.

I guess you just love your bondage huh... well not me.

OOP? NO THANKS... I'll stick with procedural design directed by simple dynamic declarative statements, and run rings around your designs in terms of performance per $$$.