This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Best way to handle multiple string replacements?
- To: "'xsl-list at mulberrytech dot com'" <xsl-list at mulberrytech dot com>
- Subject: RE: Best way to handle multiple string replacements?
- From: Kay Michael <Michael dot Kay at icl dot com>
- Date: Tue, 6 Jun 2000 18:46:56 +0100
- Cc: Sebastian Rahtz <sebastian dot rahtz at computing-services dot oxford dot ac dot uk>
- Reply-To: xsl-list at mulberrytech dot com
> With longish text nodes, this approach could result in some pretty
> deep recursion couldn't it? I once managed to crash Saxon using
> exactly this approach (although I can't duplicate that result now).
Since 5.3 Saxon uses tail recursion where it can - I think it will do so in
the recursive templates published by Jeni. If tail recursion is invoked, of
course, the depth of recursion doesn't lead to an increase in memory
requirement.
Mike K
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list