This raises the question, how should one approach the debugging of such
problems, other than by staring at the code until you see the light.
It's common enough and we've all experienced it: you write a complex expression
that looks right, and it returns nothing, and you have no clue why.
I'd suggest the following strategy:
1. Add something like
<debug><xsl:copy-of select="X"/></debug>
where X is the offending expression
2. If <debug/> comes out empty, successively remove predicates and axis steps
from X starting at the right-hand end, until you get some output.
3. When you get some output, the last step you removed was the one that was
wrong.
Michael Kay
Saxonica
mike(_at_)saxonica(_dot_)com
+44 (0) 118 946 5893
On 14 Aug 2014, at 23:28, Ihe Onwuka ihe(_dot_)onwuka(_at_)gmail(_dot_)com
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
Lord.... even after staring at the shorter version multiple times I did not
see it. It's obviously been a long long day and I should have walked away
from this ages ago.
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--