ikegami's two posts still have the problems with multiple inheritance, the super class adding in new attributes at a later date (particularly during run time. If the Super::Class gets new attributes during runtime, it'll cause problems. Yeah, yeah, using constants as opposed to strings or whatnot keeps you from defining new ones at run time, but you can still add onto the index if you're using a closure or whatnot), and serialization if the classes are changed after storing

But, again, there's nothing "wrong" with it, if you don't care about the issues. I've got no dog in the fight, so if it works for you, go for it. You just need to remember them as potential gotchas.

And jdhedden, you may have missed my point. Using arrayrefs as your object isn't re-inventing anything (lord knows it's been around a lot longer than inside out objects), but if you do want to use arrayrefs as your underlying objects, there are some more gotchas to worry about. I just decided to illustrate the ones I'd encountered back before I gave up on 'em.