Consider Design patterns as models whose basic structures can be altered to meet your design needs.
I studied C++ Design Patterns some time ago- quite a bit before beginning to learn Perl. What I gained from them were concepts of how to conceptualy break large projects into modules whose basic concepts and purpose can be communicated in a manner that is easily understood by others.
I have often found that although I come nowhere near meeting the design standards I dream of - that just the process of involving my peers in some discussion of patterns concepts stimulates our thinking use some of these concepts.
Don't be so hard on yourself and remember "Cape does not enable user to fly".
Spidey
-
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.
|