Sorry for the delay in replying. I've been a very busy WeeDom today!

The person who mentioned abstracting it off - yep,done that where possible.

Separating code/design being gospel, perhaps inappropriately - I agree. For internal webby tools it's not always worth the effort. But for a bigger web-project, particularly public-facing where design can become dated - always separate.

Indenting - I like indenting. Indenting is good, unless you're using a console-based editor where excessive indenting causes weird wrapping. But why would you? At the risk of getting flamed, there is always/almost-always a GUI alternative.

heredocs: hate 'em, hate 'em, hate 'em. Ugly things. But that's an opinion, not to be confused with a statement of fact.

My conclusion from all your comments (and thanks very much for participating in the discussion!) is that (apart from the buggy thing,and I've found the bugs and had to resort to quoted HTML to get around them) there's nothing wildly wrong with what I'm doing. My final justification is this - if you've absorbed the cost of compiling CGI.pm - why not use it? Why only use it for param() or Vars()?

Cheers,
WeeDom

In reply to Re: overuse of CGI module HTML methods? by weedom
in thread overuse of CGI module HTML methods? by weedom

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.