[EMAIL PROTECTED] wrote:
I noticed in working on changes to axiom_node_detach to ensure that the namespaces remain valid, that most of the uses of axiom_node_detach within Axis are followed immediately by an axiom_node_free_tree. It seems a shame to incur the overhead of re-declaring the namespaces in the subtree being detached, just to free them all immediately.
I think, semantically, it is correct, you want to delete a sub tree, so you detach it and then free it.
What do people think of a new combined method, axiom_node_detach_and_free_tree?
Would not this method merely call detach and then free tree?
Or, alternatively, of expanding axiom_node_free_tree to implicitly detach the tree if it is attached before freeing it? (I prefer this choice.)
This sounds OK to me. If you want to free a node, and it already has a parent, then it makes sense to detach before free. The current implementation assumes that the user is done with the node, when free tree is called, hence the need for detach and free.
Samisa... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
