Rule #1 is to always think for yourself. Of course if other people disagree with what you think, it is good to listen and try to understand why their point of view might make sense. Experiment. Be willing to change your mind. But in the end, train your judgement as best you can, judge carefully, and then think about how it worked out so that you can judge more intelligently next time.
In this case, your criticisms seem right on target. When people say use CGI or die;, they are talking about the fact that you don't want to roll your own parsing logic, because it is extremely likely to be broken. They aren't talking about the autogeneration, and most knowledgable people don't use that. Instead they are likely to suggest some kind of templating solution.
Now to train your judgement, here is my thinking on templating, for more detailed background read this white paper on Template::Toolkit, and for a list of options to make a choice from read Choosing a Templating System by our own perrin.
-
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.
|
