RE: XSL Optimizations

I don't do this currently in SAXON. I've thought about it: I think the cases
where it can help are probably rather unusual, e.g. where someone does
select="FRED" then you can determine from the DTD that if FRED children are
not allowed, the result must be empty. There may also be cases where the DTD
tells us that we can avoid a sort, or that we can stop scanning children
after a certain point. But I've got many much more basic optimisations to do
first!

There's more value in such optimisations when compiling, in the interpreted
case you have to weigh the saving against the cost of doing the
optimisation.

> -----Original Message-----
> From: Jon Smirl [mailto:jonsmirl@xxxxxxxxxxxx]
> Sent: 18 June 1999 21:55
> To: XSLList
> Subject: XSL Optimizations
> 
> 
> I'm curious, do any of the current XSL implementation use the input
> document's  DTD/schema to reduce the number of templates that must be
> checked as each node is visited? Any ideas if this optimization would
> improve the processing speed very much?
> 
> Jon Smirl
> jonsmirl@xxxxxxxxxxxx
> 
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 


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