comment on

I've been converting a script to a module, and of course, that means removing complexity from the script and putting it into the module. The module will have run modes like CGI::Application.

But the way I'm going, the entire script could look like this:

  use MyModule;
  $myobject = MyModule->new(
    lots_of_config => 'goes here'
    # etc etc etc
  );

  $myobject->go();
[download]

and the object would just figure out what mode it was in from the query string and do ... everything. The object will have its own CGI object, its own HTML::Template object and so on.

For some reason that kind of feels weird to me. When is a module too minimal? When should some of the complexity remain in the script?

($_='kkvvttuu bbooppuuiiffss qqffssmm iibbddllffss')
=~y~b-v~a-z~s; print

In reply to When is a module too minimal? by Cody Pendant

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.


Welcome to the Monastery
	PerlMonks