[Bug 24125] [xslt 3.0] intrinsically unstreamable functions


--- Comment #1 from Michael Kay <mike@saxonica.com> ---
Another problem with using "N" (navigation usage) to classify these functions
is that it causes the function to become free-ranging when used with an input
having climbing posture.

Consider the very reasonable expression reverse(ancestor::*)/name(.)

Because reverse has operand usage N this is considered free-ranging.

You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 17 December 2013 12:42:29 UTC