Hi, Robert Bradshaw wrote: > Speaking specifically of XSLT, in your framework it would be possible > to write a Transform that dumps out the tree as XML (like your > printer, but fancier), runs some XSLT on it, then reads it back in. > Most of my personal experience with XML has been unimpressive > (usually 'cause it's way to bloated of a tool than needed for the > task at hand, and slow).
Hmm, slow, is it? Tried lxml lately? It's actually a funny idea to optimise code with a tool that is itself written in the compiled language. That way, lxml would basically optimise itself. :) Also, you could easily represent the parse tree in custom classes in lxml (although not the ones that Cython currently uses). And, lxml now has XSLT extension elements, meaning, you can write your own XSLT commands in Python and do stuff that you can't do in XSLT in plain Python code, like calculating static expressions, for example. How is that for a tool? Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
