Maybe the fact that nobody has voted on Spiffy yet could be a warning sign?
To me, Spiffy is yet another way of being too clever for your own good. It is Ingys object framework, and it is mainly used for Spoon, which in turn is a nice thing for very small, very contained scripts and nothing else. I am wary of using modules that contain way too much magic, and if I were to build a bigger framework, I wouldn't rely on anything that requires a larger span of attention from Ingys part.
To address the problem you want to solve, why not just use the following code (which I use all the time):
package My::Class; use base 'Class::Accessor'; __PACKAGE__->mk_accessors( qw( foo bar baz )); sub new { my ($package,%args) = @_; my $self = { # Set some defaults foo => 'The foo', bar => 'The bar', baz => 'The baz', %args }; bless $self, $package; $self; };
That way, you don't have to pass in hashrefs to your constructor.
In reply to Re: Wanted: Spiffy evangelist
by Corion
in thread Wanted: Spiffy evangelist
by grantm
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |