[Mono-bugs] [Bug 497017] XPath ancestor set order is incorrect on mono. Correct on .NET

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Thu Jul 21 19:13:42 EDT 2011



--- Comment #1 from David Eisner <david.eisner at oriel.oxon.org> 2011-07-21 23:13:40 UTC ---
Created an attachment (id=441598)
 --> (http://bugzilla.novell.com/attachment.cgi?id=441598)
Minimal patch for XPath position() function

I will put a related fix and test cases on github for review, but this simple
patch should be enough to get your [position()=n] predicates working, if your
test case is a good representation of the problem you have in your application.
There is also a workaround, by the way, if you are at liberty to remove the
explicit reference to the position() function, as the [n] notation is actually
interpretted differently and appears to have been corrected for reverse axes.

More testing is probably needed on this, and especially for other axes such as
ancestor-or-self and preceeding. It seems, in my assessment, that optimization
attempts and uncertainty about this ordering issue have left some of this
implementation difficult to inspect for correctness and small boundary errors.

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the mono-bugs mailing list