This is the mail archive of the docbook-apps@lists.oasis-open.org mailing list .
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Well, if that mean that all keys must be recomputed on all node-set() results, beware this could cost *a lot* at runtime. What I suspect is that the keying property that you obtain from Saxon is due to the fact that nodes are reused, if you really build a new document, then it's a completely different process, a node which was a key in the first document may not be a key in the resulting node set and vice-versa, because the key will have to be recomputed from scratch. Looking at just how much (too much) processing is done by the docbook stylesheets, the fact that I implement that fully could have a very serious impact on performances, that could be true for others processors too.
At some point I may simply just drop the ball, all these node-set and
functions extensions are radical extensions from the XSLT-1.0 spec, they
*completely* change some of the assumptions I made when I engineered the libxslt implementation based on XSLT-1.0 spec, especially w.r.t. to the
lifetime of objects, scope of access of objects etc...
-- ----------------------------------------------------------------- Jirka Kosek e-mail: jirka@kosek.cz http://www.kosek.cz
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |