Re: Confusing trace from Saxon HE9

Play the video

Subject: Re: Confusing trace from Saxon HE9
From: Jeroen Hellingman <jeroen@xxxxxxxx>
Date: Wed, 09 Dec 2009 10:52:38 +0100

Thanks Michael for your explanation of tail recursion optimization.

Using the trace option helped me locate the real culprit, some template in another style sheet fragment feeding the splitter.xsl something it was not supposed to eat.

I will look into the possibility of declaring types for parameters throughout my code. In this particular instance, the $node parameter could be really any element from the source document (but not a sequence), because what I want to know is "in what output file fragment is this node rendered?", so I can generate a link to it. This can be quite tricky, considering the way I shuffle things around.

I guess I have to get the latest version of your book, as I am still using the second edition...

Jeroen.

Current Thread
Confusing trace from Saxon HE9 Jeroen Hellingman - 8 Dec 2009 19:59:25 -0000 G. Ken Holman - 8 Dec 2009 21:05:27 -0000 Jeroen Hellingman - 8 Dec 2009 22:06:44 -0000 Michael Kay - 8 Dec 2009 23:17:32 -0000 Jeroen Hellingman - 9 Dec 2009 09:53:06 -0000 <= Michael Kay - 9 Dec 2009 10:26:31 -0000

<- Previous	Index	Next ->
RE: Confusing trace from Saxo, Michael Kay	Thread	RE: Confusing trace from Saxo, Michael Kay
Re: What short short XSLT 2.0, Dimitre Novatchev	Date	RE: Confusing trace from Saxo, Michael Kay
	Month

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Subscribe in XML format

RSS 2.0
Atom 0.3

XML Editor - Download a 15 Day Free Trial Now >

See What's New in Stylus Studio >

Buy Stylus Studio - XML Editor - Now >