DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=23957>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=23957

Appears an infinte? loop causes stack overflow.





------- Additional Comments From [EMAIL PROTECTED]  2004-05-31 21:34 -------
It looks like there really is an infinite recursion in your example.  Given the 
design of the Xalan-Java Interpretive processor, it's not clear what other 
result could be produced.

You've voted for this bug, so you must feel that it's important.  Any thoughts 
about what would be a better result?

By the way, the cause of the infinite recursion is in the way the 
generate.colgroup template is called in the definition of the colgroup variable 
in docbook-table.xsl.  It sets the cols parameter to the node-set produced by 
the expression @cols.  There is no cols attribute in the input document, so it 
returns an empty node-set.  The recursion in generate.colgroup is broken when 
$count > $cols.

According to section 3.4 of XPath [1], "If one object to be compared is a node-
set and the other is a number, then the comparison will be true if and only if 
there is a node in the node-set such that the result of performing the 
comparison on the number to be compared and on the result of converting the 
string-value of that node to a number using the number function is true."  The 
node-set in the cols variable is empty in this case, so there is no node for 
which the comparison is true; therefore, the comparison is always false, and we 
never break the recursion.

I'm sorry that this response is coming so late.  Perhaps you've already 
resolved the problem.

[1] http://www.w3.org/TR/xpath#booleans

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to