in reply to Re^4: hrm, Eval::Compile
in thread hrm, Eval::Compile
Ok... here is an example, I haven't used this technique for a while but it has been useful before.
<refas tag="foo">/path/to/bar.xml</refas>
Where bar is an xml file containing some values, and refas creates a new plugin on the fly called foo, which substitutes any foo tags it finds in the document with the values they specify, adds it to the command list and restarts the parser.
Once that command is triggered, anywhere in the document that the tag <foo>x</foo> or <foo>y</foo> exists get substituted for the values contained in foo : <y>somevalue</y>, <x>somevalue</x>.
The <SQL tag supports a refas mode which uses the columns of the database for the key.
Another example is that it is possible to build tags on the fly for example :
<<qd>gettype</qd>> somedata </<qd>gettype</qd>>
Where gettype can be either html or xml, giving either:
<html> somedata </html> or <xml> somedata </xml>
If you can't determine ahead of time what a given tag actually means because it's meaning might be changed at runtime by another tag which branches on the request data, how can you compile it?
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^6: hrm, Eval::Compile
by Corion (Patriarch) on Jul 20, 2011 at 13:56 UTC | |
|
Re^6: hrm, Eval::Compile
by Anonymous Monk on Jul 20, 2011 at 22:47 UTC | |
by Logicus (Initiate) on Jul 21, 2011 at 00:26 UTC | |
by Anonymous Monk on Jul 21, 2011 at 01:13 UTC | |
by Logicus (Initiate) on Jul 21, 2011 at 02:53 UTC |