IMHO they are the same as for any other software design fad: On a small scale, keep functions to about a page (80x24), and make them do one thing. On a large scale, organize things into modules corresponding to tasks. In your case, I would look at breaking a chunk of the script off into a separate module, which doesn't have to be in "I can has objects" style. If you later need more than one simultaneous instance of that module, you can always objectify it then.
Above all, don't get hung up on dogmas like "I need objects," "global variables are evil," etc. These are just vague guidelines, and are useless unless you understand why they are sometimes true.
-
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.
|
