I have been a fan of Class::Std but if I was to look at another module I would consider Class::InsideOut.
The more I worked with objects, the more I believe in using inside-out objects. It keeps you and your co-workers from being able to do stupid stuff(like directly accessing object data).
I also like to work with get_* and set_* methods rather than one method that can do both. A number of method generators don't have that option and don't play well with inside-out objects, relying more on blessed hashes.
Another issue is whether your object is going to represent data from a database. There are quite a few distributions for doing that, but I have not been happy with most of them and ended up writing my own. I have recently gone back and took a look at them again and one that is striking my fancy is Rose::DB::Object. The document and syntax is reasonably clear so I will probably start looking at that seriously.
In reply to Re: Object oriented Perl: What's popular?
by Herkum
in thread Object oriented Perl: What's popular?
by amarquis
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |