My program will not require changes. (Although, I
can forsee the possibility where it would be useful to scan
student marks into one database and then scan books into
another. OTOH, I should work on my Laziness before I start
worrying about Impatience.) You seem to be saying that
modules are a good way of simplifying design issues.
Module Interface design: (never having written a module)
Should I put all of my different database connections in
one module, my input methods into another and keep the
logic in the main program? Going through the Cookbook, I
still don't see in what manner I should divide up my program into
different modules.
-
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.
|