Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
IMO it's more "future facing" to use a loop on @ISA and the can method.
It enables the Object to handle multiple inheritance.
$self->$_($params) for ( map{ $_->can("_init")||()} @ISA );
This'll execute a "private" method to initialise the correct variables for the object.
As a rule, I pass all Parameters for the function inside a hashref called $params, it makes for easier coding and ledgibility.
I generally have a class property called @manifest, listing the object properties and use a line like:
$self->{$_ns . $_} = $params->{$_} || '' for @manifest;

Where $_ns is the namespace as all the gubbins is stored in one hash, it's best not to overwrite stuff.
I use a class property like this:
my $_ns = __PACKAGE__; 
For I find there are times when __PACKAGE__ doesn't want to play.
I also apply accessor and mutator functions for all the properties:
sub get_spong() { $_[0]->{ $_ns . 'spong' } }
And because all of this is labour-intensive and boring,
I set up a template and also some generic parent classes to ingherit most of the common stuff from.

As a rule of thumb Perl OO is tricky, because it's Perlish OO.
You can rewrite OO from first principals.
Perl OO can be clunky: it mirrors the developers understanding of OO principals since Perl is so liberal.

--

Brother Frankus.

¤


In reply to Re: inheritance: constructors by frankus
in thread inheritance: constructors by Basilides

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others admiring the Monastery: (6)
As of 2024-03-28 13:45 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found