That's fine if you want a bunch of different .cgi scripts. But, if you want them all in the same script for some reason, perl gives you lots of rope to do this with.
sub setup {
my $self = shift;
for my $table in (@tables) { # define @tables elsewhere
$self->run_modes(
"c_$table" => sub { $self->do_c($table); },
"r_$table" => sub { $self->do_r($table); },
"u_$table" => sub { $self->do_u($table); },
"d_$table" => sub { $self->do_d($table); },
);
}
}
Different .cgi scripts is great when you're giving your C::A-based module to others to use, as it provides some simple flexibility to the middle-man. But, I'm not so fond of it for general use. They actually confuse me. Maybe I'm easily confused about this, I suppose. Either way, this is just another WTDI.
