Re: Recursive replacement


  Well, the constructor "element new-node {$p/*}" copies the contents of
  the node $p, so the outermost <a/> node is replaced with

Yes but the question is really about the inermost a node.
Michael indicated that the table is intended to allow the operations
that commute, so it depends a bit on what the definition of equivalence

If you replace the inner one first, then the outer one, then the effect
is as if you just replaced the outer one, as you indicate above.

If however you replace the outer one first, when you come to replace the
inner one, it's not there, so is that a merge conflict and an error, or
do you just silently do nothing in which case commutativity is
restored, and you get the same result as if you had done the operations
in the other order.


This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:

Received on Monday, 30 January 2006 15:43:56 UTC