You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2004/11/02 01:55:37 UTC
DO NOT REPLY [Bug 4721] -
Programmer's assertion in getNextStepPos: unknown stepType: -1
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=4721>.
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=4721
Programmer's assertion in getNextStepPos: unknown stepType: -1
lars@huttar.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
------- Additional Comments From lars@huttar.net 2004-11-02 00:55 -------
I feel otherwise (Re: Joe's comment). I was bitten by this error message too.
Even though I, and Yannick, and George, had committed syntax errors, that does
not mean that this error message is not a bug. "Unknown stepType: -1" gives no
clue as to what the error is. As most programmers have experienced, unhelpful
error messages can lead to hours of frustration and lost productivity. It's not
my intent to rant, just to emphasize that just because the programmer has
committed a syntax error doesn't relieve the processor of all responsibility to
respond in an appropriate way.
This is one reason I like to keep Saxon around: when Xalan gives an error
message that doesn't help, Saxon usually does a better job. In this case, I had
an incomplete XPath expression in a test:
<xsl:if test="$entity/*/access[@role = $role and (@function ='none' or
@function = 'read')] and">
(note the "and" with nothing after it).
I only discovered this because Saxon gave the error "E Error in expression
$entity/*/access[@role = $role and (@function ='none' or @function = 'read')]
and: Unexpected token EOF in expression model.xsl
file:/C:/Program%20Files/Apache%20Group/cocoon/mount/gem3/standards/r3/c2/model.xsl
53:0"
Very helpful.
So, the suggested fix would be to print an error message that gives indications
of what would have caused this condition.
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org