Currently unspecified: Cursor normally has clear semantics for most methods:
when you call a method, the cursor either moves, or it does not. The write
method (and the new typed write method on TypedCursor) do not specify
semantics. As a consequence, the cursor may be positioned anywhere following
the write. Currently, all bridges do not move the cursor. However, expecting
this behavior would be wrong; one would actually *expect* the cursor to be
positioned "after" the origin node, assuming that it uses cursor semantics to
walk the tree.
This should be defined and resolved before the 1.0 release.
Original issue reported on code.google.com by aale...@gmail.com on 30 Jul 2012 at 7:59
Original issue reported on code.google.com by
aale...@gmail.com
on 30 Jul 2012 at 7:59