I'm not sure that's entirely true. Node-sets usually contain nodes from
the input document. RTFs, on the other hand, are created by the processor
on-the-fly as a separate "mini-document." So, unless a processor is
incredibly clever, it will have to copy the nodes from the input node-set
into the RTF, and that's never going to be the cheapest operation.
yes building the rtf involves copying nodes (or building new ones)
and is arbitrarily expesive depending on what you're doing but
I just meant that th eopreration of converting an rtf to a node set
is likely tio be cheap constant time thing that doesn't involve walking
over the tree.
I do agree with you that the actual operation of converting an RTF
to a node-set is likely to be very cheap.
which is all I meant to imply, sorry if I wasn't clear.
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list