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.
-
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.
|
