I go one step further than "fly weight objects". I take a
lexical hash for each attribute, and index those with the
object. This means you never have to use string literals to
access attributes (and hence you get the full benefit of
using strict), and you only need one hash query instead of
two to access the attribute.
Here's my implementation of the BaseballPlayer::Pitcher class.
It's totally independent of the implementation of the
BaseballPlayer class (although it could be that you want to
mask the constructor - but that's ok because the constructor
is part of the API). I call this technique "Inside Out Objects"
(people who saw my presentation at YAPC know all about it).
package BaseballPlayer::Pitcher; {
use vars '@ISA';
@ISA = 'BaseballPlayer';
my (%ERA, %Strikeouts);
sub ERA : lvalue {$ERA {+shift}}
sub Strikeouts : lvalue {$Strikeouts {+shift}}
sub DESTROY {
my $self = shift;
delete $ERA {$self}, $Strikeouts {$self}
}
}
Abigail
-
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.
|