It would just set up the skeleton based on variables passed to it. and print out out something like:
The config file would look something like this:use Moose; use this; ust that; has this => (is => 'ro', isa => 'that'); sub do_this { my $self = shift; confess 'not implemented'; }
$use = ['Moose, 'this', 'that';] $attributes = {name => 'this', {is => 'ro', isa => 'that'}; $methods = ['do this'];
Maybe a templating system is better with some kind of vim plugin in. I just don't know. I'm sure this kind of thing has been done before. I'm not trying to reinvent the wheel just trying to figure out which wheel to use for this task. All I know is I'm bored stiff typing out the same thing over and over and fixing dumb typos which eat up a crap load of time. I'd rather just focus on constructing the building instead of setting up scaffolding.
$PM = "Perl Monk's";
$MCF = "Most Clueless Friar Abbot Bishop Pontiff Deacon Curate";
$nysus = $PM . ' ' . $MCF;
Click here if you love Perl Monks
In reply to Re^2: Automation of testing of Moose class structure
by nysus
in thread Automation of testing of Moose class structure
by nysus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |