Saxon

Legacy ID: #4879307 Legacy Poster: Inigo Surguy (inigo)

Hi, Is Saxon.NET 9.0.0.2 expected to perform tail-call optimization on a recursive call-template? When invoking Saxon.NET via ASP.NET inside IIS, I'm getting an IIS process crash when running a tail-recursive call-template (the same code works fine when invoked directly from VS.NET or from Oxygen). This seems most likely to be because there's a stack overflow: and for some reason, VS.NET and Oxygen have a larger stack available than the IIS process does. Ah - the other possibility is that my XSLT isn't being recognized as tail recursive. The recursive call I'm making is: <xsl:for-each select="preceding::*[1]"> <xsl:call-template name="myTemplate"/> </xsl:for-each> If Saxon doesn't recognize that the for-each can only have one value, then I imagine it wouldn't recognize it as tail-recursive. I've worked around the problem in my XSLT already; I just wanted to raise this as a possible bug/enhancement. Thank you! Inigo