comment on

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); },
    );
  }
}
[download]

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.

In reply to Re^2: avoiding excessive number of methods in CGI::Application and DBI modules by Tanktalus
in thread avoiding excessive number of methods in CGI::Application and DBI modules by aroc725

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


laziness, impatience, and hubris
	PerlMonks