So it is far from trivial to safely output text from a plugin that looks like aXML but is not interpreted as aXML again.
I would reconsider this design choice because you might end up with problems ranging from annoying problems like not being able to use aXML to generate XML and aXML, to really big security holes like user generated content triggering internal aXML code.
Of course, proper documentation on how to generate various output would also help, and also the replacement rules when aXML turns & into &, < into < and when it passes them through.
In reply to Re^29: aXML vs TT2
by Corion
in thread aXML vs TT2
by Logicus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |