Favorite object-oriented modules?

[Tim McDaniel]

I asked about Moose and got comments that it's slow. Is anyone
willing to talk about other favorite modules for Object-Oriented
Programming in Perl?

"Favorite" is, of course, subjective.

Personally, I am inclined to prefer modules that handle more things
correctly, safe coding in general. For example, I like inside-out
coding, because I like catching typos as early as possible. Also, I
don't like to code destructors or any other housekeeping code, because
of the effort and the possibility of getting something subtly wrong.

 

[Tim Greer]

I asked about Moose and got comments that it's slow. Is anyone
willing to talk about other favorite modules for Object-Oriented
Programming in Perl?

"Favorite" is, of course, subjective.

Personally, I am inclined to prefer modules that handle more things
correctly, safe coding in general. For example, I like inside-out
coding, because I like catching typos as early as possible. Also, I
don't like to code destructors or any other housekeeping code, because
of the effort and the possibility of getting something subtly wrong.

I can't imagine anyone liking a specific module more or less, just
because it's OO. I also think most would agree that a well coded, well
thought out, mature, stable and secure module is best, regardless of
being OO or not. Overall, I don't care, if it's well coded and can
save time and fit into a project and I can use it (and trust it).

What I dislike, however, is when people use OO just for the sake of OO,
when it doesn't provide any advantage. Of course, those are usually
the same type of people that will create a project with 100 custom
modules, each doing one specific (and very similar) task, where it
makes it a huge hassle to take over a project when that person
ultimately doesn't work out and you have to go through 20 files just to
be able to fully understand what one single function is doing. Then
again, I've yet to see any Perl module in CPAN where someone went crazy
about it to that degree, so I'm speaking from the perspective of
developing with other people that do go crazy and not CPAN modules.

 

[Ron Bergin]

What I dislike, however, is when people use OO just for the sake of OO,
when it doesn't provide any advantage.  Of course, those are usually
the same type of people that will create a project with 100 custom
modules, each doing one specific (and very similar) task, where it
makes it a huge hassle to take over a project when that person
ultimately doesn't work out and you have to go through 20 files just to
be able to fully understand what one single function is doing.  Then
again, I've yet to see any Perl module in CPAN where someone went crazy
about it to that degree, so I'm speaking from the perspective of
developing with other people that do go crazy and not CPAN modules.
--

That's a common problem I've seen from Perl programmers that learned
that "style" from the language formally known as "Personal Home
Page". )

 

[Tim McDaniel]

I can't imagine anyone liking a specific module more or less, just
because it's OO. I also think most would agree that a well coded,
well thought out, mature, stable and secure module is best,
regardless of being OO or not.

I suppose I was unclear. I am asking about modules that can be used
to implement object-oriented programming: Moose, Class::InsideOut,
Object::InsideOut, Class::Spiffy, whatever.

 

[Tim Greer]

I suppose I was unclear. I am asking about modules that can be used
to implement object-oriented programming: Moose, Class::InsideOut,
Object::InsideOut, Class::Spiffy, whatever.

Oh, sorry I misunderstood. Got ya.