What would a good real world example of why you would use XSLT over Perl?
When the system you want to render the XML may not have perl.
Seriously, the power behind XSLT is that it's simple. It's designed to be generic, so that it can be implimented in any number of ways, by any number of systems. You can send a browser an XML file and an XSLT, and trust that the browser can apply it regardless of how that browser was implimented. Or you can use XSLT to generate a report from a bunch of a data, and know that as long as the data format doesn't change, the report format won't change .. even if the reporting systm gets re-implimented by 40 different people.
Perhaps a better way to explain it is like this...
XSLT is to language specific templating systems, as XML is to language specific data structures....You could write an application that saved all of it's data with "use Storable;" and that would be a perfecctly valid design decission if you were 90% confident that no one would ever want to read that data except with a perl program. Or you could use something like XML, and not care what laguage they use. The same is true for XSLT and rendering your data: if you are 90% sure all you ever want is to use perl, then there are probably simpiler ways to do what you want ... or you can use XSLT, and not care what langauge people use to render your data.
In reply to Re: Why XSLT and not just Perl?
by hossman
in thread Why XSLT and not just Perl?
by blahblah
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |