I'll be over here writing less, easier-to-maintain
"Less" and "easier-to-maintain", as long as your requirements don't change. OO isn't about reducing complexity, it's about managing it. We should expect to write more code now in order to simplify things later.
In your temperature example, having the setTemperature method do all the conversions, you've forced yourself to doing all the conversions in a single method (perhaps dispatching to other internal methods to do the conversion via a lookup table). If you need to convert to some other scale, you have to add in that code within that method.
If you using a Temperature class instead, the conversions are all inside that method. One method does exactly one conversion. Much easier to maintain.
easier-to-use
$obj->setTemperature({ celsius => 50 });
Or:
$obj->setTemperature( Temperature->new({ celsius => 50 }) );
A little more typing. It's other benifits make it worth it.
possibly more efficient OOP code
If you're that concerned about efficiency, why are you using Perl's bless'd OO?
----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer
: () { :|:& };:
Note: All code is untested, unless otherwise stated
|