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 });

[download]

Or:

$obj->setTemperature( Temperature->new({ celsius => 50 }) );

[download]

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

In reply to Re: Re: Re^9: OO Getters/Setters by hardburn
in thread OO Getters/Setters by theAcolyte

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.