So, the problem is that when run from the command line Saxon does not
include the time for xsl:message instructions in the time it reports
when the -t option is specified. However, if Saxon is invoked by
another application (the XSelerator in my case), although the same
command-line string is used for the invocation, the time reported by
Saxon includes the time for the xsl:message instructions.
That's an interesting theory, but I don't think it's true. I think a more
plausible conjecture is that the performance of xsl:message depends strongly
on the message destination, and that it's the choice of message destination
that actually affects the result.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--