What are the pros and cons of an Inside-Out Object Model?
Pros:
- Encapsulation of attributes: only the scope that defines the attributes can get at them.
- Inheritance always works: the implementation isn't dependent on how a super class is implemented.
- Multiple inheritance is potentially easier.
Cons:
- It's more complex, you need for instance a DESTROY function.
- By default, they don't work after splitting of threads, unless you set up a special CLONE method. (They should work fine if you only create objects after you've split up your threads).
- Due to the encapsulation, you will need to do extra work when serializing.
- There's far less documentation. "Everyone" still gets to learn hash based objects when learning OOP in Perl.
-
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.
|