3 ms·
Perhaps the lack of a good substitute is why the author is so frustrated. Also, given that he works for a XML document processing company, I don't think he want
by aristidb 15y ago
Perhaps the lack of a good substitute is why the author is so frustrated. Also, given that he works for a XML document processing company, I don't think he wants to use XSLT as a general purpose language.
- notalbert 15y agoI think plain old SAX makes a good substitute. It only lacks one (of the two) good things I like about XSLT, template matching. But Fowler suggests a way to get that: http://martinfowler.com/bliki/MovingAwayFromXslt.html http://martinfowler.com/bliki/MovingAwayFromXslt.html The other thing I like about XSLT is that it creates a hard code-boundary. But I hardly think its syntax makes that worth it.