This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Want to process XHTML in my XSL stylesheets.


> Yes - I'd assumed that you would simply flag the over-dynamic cases as 
> generating invalid content, but as you say, it's quite possible that 
> there will be cases which in fact are valid but are undecidable by any 
> program of sensible complexity.

I'd guess it has to be "undecidable by any program" (period).  Given that
XLST has been shown to be Turing complete (for XSLT 1, but I'd guess the
same for XSLT 2 ?) it would seem a pretty straight forward proof that there
always exists an XSLT that is undecidable (ie; not all results can be
determined in advance)?


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]