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
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, 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, 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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|