note
jplindstrom
I buy that.
<p>
But it's not a far stretch to use very very light-weight classes and use a simple hash for the properties until you need something more. This is an entire class in a small steal-entries-from-http://buzz.bazooka.se/-and-fake-email-posts-to-our-internal-bullshit-list-at-work program I wrote for the fun of it after a coffe break discussion:
<p>
<code>
package Buzz::Post::Comment;
use HTML::Entities;
sub new { my $pkg = shift;
bless(my $self = { @_ }, $pkg);
$self->{text} =~ s{<br />}{\n}gs;
$self->{text} = decode_entities($self->{text});
return($self);
}
</code>
<p>
It's not really a serious class in that you can't see what properties there are, there is no documentation, no visible interface to new() etc.
<p>
But the benefits I get are:
<ul>
<li>No hassle, it's almost like just using a hash
<li>OO thinking, which is the way I work
<li>A good name. That's always worth a lot
<li>Somewhere to put my methods instead of in the pile of subs
</ul>
<p>
Basically it's the same laid-back scripting attitude, but with a touch of structure.
<p>
/J
396759
397345