Cart
[Home] [By Thread] [By Date] [Recent Entries]
David Carlisle wrote:
yes that's the expected behaviour (although of course it's nothing really to do with the xsl:sort, a more direct case is I knew that it wasn't allowed explicitly. However, in the example I gave, the child nodes of the rows-node are ordered based on their text() child. I realize now that this never selects anything on the attribute axis (having no children) and thus returns an empty sequence, which ends up at the start of the ascending sort (which causes no problems). Reversing the sort places it at the end, causing the error. sounds all in all quite logical eventually. It's required to allow an implemenation to start serialising the result Thanks for this explanation. I often wonder the "why" behind a given feature of the spec, this makes it sound so more plausible. Cheers, -- Abel Braaksma
|
