As I use Moose more, I've found it is easy to use some of its mechanisms in ways they probably were not intended to be used and that this can lead to confusing code. One of the things I've been doing is to use the BUILD method to set object attributes. For example, I've got this:
package 'Blah'; use Moose; has attributes => ( isa => 'HashRef' ); has attr1 => ( snip ); has attr2 => ( snip ); has content => (isa => 'HTML::Element'); sub BUILD { my $s = shift; # add attributes to object and/or HTML::ELEMENT in content attribute foreach my $attrib (keys %{$s->attribs}) { # set attributes of an object if it exists if ($s->can($attrib)) { $s->$attrib($s->attribs->{$attrib}); } # set attributes of #HTML::ELEMENT } else { $s->content->attr($attrib, $s->attribs->{$attrib}); } } }
In one way this is convenient as I can just smash all the attributes into one hash and let the class figure out how to process it. I'm now rethinking this, however. I'm wondering what others think. Thanks!
$PM = "Perl Monk's";
$MCF = "Most Clueless Friar Abbot Bishop Pontiff Deacon Curate Priest";
$nysus = $PM . ' ' . $MCF;
Click here if you love Perl Monks
In reply to Is setting attributes with BUILD in Moose a bad idea? by nysus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |