RE: Re: Re: xsl:for-each evaluator?

> 
> One *cannot know* if a program will terminate -- unless this 
> property has a strict proof.

That's true in general. But there is a large class of stylesheets for
which you can prove termination: anything that only selects downwards
will finish in finite time if given a finite source document.

It's not clear what the OP was asking for, but I don't think he wanted
static analysis, just some kind of instrumentation.

There's tracing in Saxon, including a tool that gives you a trace with
timing information, and a stylesheet for analyzing the trace output.
Unfortunately the timing information you can get from Java is very
coarse-grained, so it's of limited use.

I find the best approaches to timing analysis are

(a) measure performance with different sized source documents to see how
it scales.

(b) remove things one by one from the stylesheet until you find the
thing that's causing it to run slowly.

Michael Kay
 


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