No. In wading through the Class:: heirarchy, I missed that. Of course, it fails the "simple" test and while it gives me a bit of flexibility on my object's internals, it still exposes them. This exposure means that once I've chosen my object's internal represenation, I have to switch to a different Class::MakeMethods subclass if I need to change them (and I've had to change internals before). I also don't see any explicit argument validation available.