Problems? Is your data what you think it is? | |
PerlMonks |
Re^4: Help understanding object constructors (by Perl Best Practices book)by dragonchild (Archbishop) |
on Nov 07, 2005 at 17:05 UTC ( [id://506440]=note: print w/replies, xml ) | Need Help?? |
Not playing nice isn't necessarily a bad thing. However, it is still a reason why I choose to use hash-based objects in most of my programming. The ability to debug w/DD is a very nice thing indeed.
Class::Std is, first off, not thread-safe. Second, if I inherit from Class::Std to create my own OO model based on it and I don't call SUPER in the DESTROY, there's a memory leak. (It's pathologically idiotic, but it's there.) My benchmark numbers are simple ones from playing with it and what I've seen reported. I will gladly stand corrected given the responses I received. As for subclassing, Damian has tried to work around the problems when two attributes are declared with the same name in the same hierarchy. But, that's still a problem. While you and I both know that it's a problem inherent to inheritance and composition in general, people cite inside-out objects as a way of avoiding hashkey clashes (which it is), then conclude that it's a way of avoiding attribute clashes (which it isn't). I was merely making that point explicit. My criteria for good software:
In Section
Seekers of Perl Wisdom
|
|