I'm working on an average-sized CGI app using CGI.pm and DBI, amidst other less relevant modules. It makes heavy use of tables and class definitions, and I'm currently printing them all out using heredocs.
I'm using CGI.pm to handle cookies and POST variables, but my question is, is there any compelling reason for me to go back through and change all of my working HTML heredocs to their CGI.pm equivalents? Keeping the HTML cross-platform isn't a concern.. This is going to be intranet-only in an all-Microsoft company, and I've been fairly conscious of compatibility issues when coding.
This is something I've always wondered about, since everyone always shouts "Use CGI.pm!!" when a CGI question is asked, and I whole-heartedly agree when it comes to form parsing and cookies, but is it a big deal to just print out your HTML?
-
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.
|
