So you're saying that, instead of stacking compiled functions as anonymous code, like Higher Order Perl does, you stack strings and constantly evaluate them? Unless I misunderstand your approach, I don't see the advantage of your approach over the approach of Higher Order Perl, which uses callbacks instead of template strings. If you use flat strings, you forego the possibility to have structured data.

As a side point, trying to explain your technique using terms such as "black magic" is not helpful. Any sufficiently advanced technology is indistinguishable from magic, but if you want to get people to understand or use your special brand, you will need to explain the technology or mechanics behind what appears as magic, whether black or whatever colour you choose.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.