As requested in ticket #124, variable interpolation in XML comments has
been implented in version 0.9 or so. However, ticket #149 shows that
this can be problematic if you comment out a section like this:
<!--
<select size="1" name="item" >
<option py:for="x in mylist" value="$x">$x</option>
</select>
-->
Kid still tries to evaluate the variable x which is undefined because
the for loop does not run inside the comment.
Any ideas how to reconcile both tickets? One idea is to interpolate
variables only if there is no py:attribute and no processing instruction
inside the comment (as in the use cases in #124). Better ideas?
-- Chris
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
kid-template-discuss mailing list
kid-template-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kid-template-discuss
