with
@stack = ( ['cfif', 'bool eq "true"'], ['cfelse'] );
the subs could start with something like
sub start { return if $stack[-1][0] eq 'cfif' and $tag ne 'cfelse' and not istrue +($stack[-1][1]); return if $stack[-1][0] eq 'cfelse' and istrue($stack[-2][1]); } sub end { return if $stack[-1][0] eq 'cfif' and $tag ne 'cfif' and not istrue(. +..); return if $stack[-1][0] eq 'cfelse' and istrue(...); } sub text { something like what i used in start() }
This piece of pseudo-code doesn't handle nested cfif's, but nothing is impossible. Maybe the bool eq "true" syntax is too hard for HTML::Parser, but nesting and ignoring will of course be up to you, just like when you use your own parser.

2;0 juerd@ouranos:~$ perl -e'undef christmas' Segmentation fault 2;139 juerd@ouranos:~$


In reply to Re: Re: Re{4): Template Parsing - Finding tag pairs. by Juerd
in thread Template Parsing - Finding tag pairs. by vladb

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.