comment on

You could always use a hash of coderefs to make a jump table.

my %query_to_sub = ( officeID => \&edit_office_product,
                     fnord    => \&vreemflitzel );
$query_to_sub{ $query->param( 'spoo' ) }->()
[download]

Or if you've got a module, just call the apropriate method on it (if it can()).

my $method = $foo->can( $query->param( 'behavior' ) );
if( defined( $method ) ) {
  $foo->$method()
} else {
  do_error( "Unknown method " . $query->param( 'behavior' ) );
}
[download]

Of course if you're going to get OOPy this would be something you could use a State/Strategy to represent the behavior (which reminds me I really should write a review of Design Patterns and Refactoring like I've been meaning to for a while now . . .).

In reply to Re: Would you use 'goto' here? by Fletch
in thread Would you use 'goto' here? by Ovid

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.


Just another Perl shrine
	PerlMonks