Now first of all I'll calmly say that you should be using the template toolkit or HTML::Template for all you html templates.

Now here is how I would write that snippet of code if I was crazy enough to try to write my own template system.

while (<TEMPLATE>) { s/<~([^~]*)~>/$1/eeg; print; }
This evaluates $1 to produce $varname, then evaluates $varname to produce its contents. I don't see what s///i is doing since I didn't know that any of the characters <>~ could have multiple cases. And because of the [^~] it shouldn't have a problem with multiple instances on the line (yours would read all non >'s on the line including '~', and THEN look for '~>', then backtrack so it would probably still work though but not as quickly or clearly).

In reply to Re: Regex and HTML Question by repson
in thread Regex and HTML Question by r.joseph

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.