Subject: [xsl] What VAST areas of knowledge must be integrated to create an XSLT processor? From: "Roger L Costello costello@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Date: Mon, 10 Mar 2025 16:33:09 -0000 |
Hi Folks, Last week there was a discussion on using XSLT to display the set of Unicode characters denoted by a regular expression. Unicode? Regular expressions? Those are two VAST areas of knowledge. An XSLT processor implementor must have a mastery of them and must know how to incorporate Unicode and Regular Expressions into his implementation. XSLT operates on--parses--XML documents. Parsing? Parsing is a VAST area of knowledge. An XSLT processor implementor must have a mastery of it and must know how to incorporate Parsing into his implementation. Then there are the languages themselves--XSLT and XPath. XSLT? XPath? Those languages are VAST. An XSLT processor implementor must have a mastery of them and must know how to incorporate XSLT and XPath into his implementation. The amount of knowledge that must be integrated to create an XSLT processor is MINDBLOWING. What other VAST areas of knowledge must be integrated to create an XSLT processor? /Roger
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Imagine that the semantics of, Roger L Costello cos | Thread | [xsl] Is there a way in XSLT/XPath , Roger L Costello cos |
[xsl] Imagine that the semantics of, Roger L Costello cos | Date | [xsl] Is there a way in XSLT/XPath , Roger L Costello cos |
Month |