...I agree here. I've always been reluctant to encourage students too strongly to use the output functions in CGI.pm because some of them will have to maintain their code. And I couldn't find any great rationale for the extra effort that would be involved in writing code to essentially spit out HTML that you'd have to form anyway in order to get the function to produce it.
There are rare occasions in which it is useful to spit out a small section of HTML from the module functions, and I hadn't considered the very valid point in the original posting here that the module does allow poorly formed HTML to be noticed more easily.
But as a general rule, there's usually a better way to embed the HTML in your code. And of course if you're working on anything that transcends the trivial, you'll want a template. Another post here addresses that nicely.
---v
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.