Jeff wrote : > By adding a $foo:noescape syntax, it would only be necessary to add the > property to the node and some code to check it in ASTReference.
Yes, but you have other ways to avoid char escaping than to introduce a new syntax. For instance, you can set the content format of the outer template to be "text/plain". If you need a fine-grained control of your own on whether or not escaping is occuring, I guess you should write a tool to fullfit your needs. > My question: Why track the state of text outside of references? With a > $foo:noescape option, the person writing the template can easily control > the appropriate behavior inside of CDATA sections and the like. As a > reference point, neither Struts nor JSTL have (or seem to require) this > additional intelligence. You need to track the state because you not only have to know whether to escape chars or not, but which kind of escaping should occur (for instance : single quoted vs double quoted strings). My aim here is to free designers from the painful task of choosing the right escaping at the right place, and again this kind of control can easily be done using a tool. CloD -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
