For what it's worth, I am a fan of polymorphic getter/setters, but I autogenerate them rather than writing them individually:
- if the field is immutable, the method knows it and generates an appropriate error message (but you can set key fields on newly created objects that don't yet have them set);
- they detect if the setting actually changes the value, and record the fact;
- when setting, derived values are invalidated;
- when getting, a not-yet derived value is calculated and cached;
- they are generated into an intermediate class, so the concrete class can override them simply (though overrides must call the SUPER:: method appropriately);
- they don't yet auto-generate documentation, but they could do so.
Nothing here that couldn't also be done with separate getters and setters; the two main benefits are the avoidance of code duplication, and the ease of iterating over the fields.
I agree with you about tie and lvalue though. :)
Update: I forgot the one time I have profitably used tie: package MyApp::Log;
my $log;
sub enable { ...
$log = MyApp::Log->new($context);
tie *STDERR, 'MyApp::Log::STDERR';
... }
{
package MyApp::Log::STDERR;
sub TIEHANDLE {
my $class = shift;
bless {}, $class;
}
sub PRINT {
my $self = shift;
$log->die(join '', @_);
}
}
for those things not caught by $SIG{__(WARN|DIE)___} handlers.
Hugo
-
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.
|