Oh, I don't know about that. The frustration in failing to remember to update my call to run_modes whenever I add a new run mode function is probably worth those extra few letters on each and every function name. It can save me minutes of debugging time, which is way less effort than typing three extra characters.

Further, by the principle of keeping scope as minimal as possible, everything to do with a given run mode can be kept to just that function - I don't need to remember to go to the top (or bottom) of my module to add it to another data structure elsewhere. Having to set up run modes has to be my biggest issue with using C::A. Not that I have a better solution, mind you. It just is.

In reply to Re^2: CGI::Application - A little too lazy? by Tanktalus
in thread CGI::Application - A little too lazy? by friedo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.