You might design the industry-strength application?
Actually you need modularity and scalability then.
The application should remain maintanable and flexible.
You do need design patterns!
But be aware that Perl design patterns are quite idiomatic:)
They differ from C++ design patterns.
So use the perlish patterns and build the application.
The key word is 'to build' the application instead of to 'to code'.
There is an entry point:
http://www.slowass.net/wiki2/assemble.cgi?PerlDesignPatterns
The good idea is to avoid them all at once.
Different layers require different set of patterns.
And different application scale also want various approaches.
Thats it.
-
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.
|