Wow, that turned out to be a very engaging read -- thanks.
I think my strongest reaction involved this point, and all the places you went as you pursued it:
A template is just a program, but you quote the code, not the output.
Well, not exactly. Based on the established wisdom of separating data/content from code, a template is a way of representing the content in a manner that is compatible with, yet still separable from, the code. A lot of stuff is needed in the code that really just does not belong in the template, just as there's a lot of stuff in a template that does not belong in code.
Your various gyrations in templating syntax, to support a dizzying assortment of coding constructs within the template data, all end up (from the sound of it) as an elaborate way to obfuscate the displayable content of the template files. But if it cooks for you, hey, who am I to knock it? ("++" in any case)
I realize you've only given a very cursory description of some of the details, but I had to wonder what the documentation must be like for such a system, and how long it would take someone besides you to grok it.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||