DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3489>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3489 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Keywords| |TestID, XSLTBug Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2001-09-14 12:23 ------- Still happens xml-xalan CVS 14-Sep-01 as described TestID: Bugzilla3489.xsl checked into tests/bugzilla Hey! This is actually correct behavior! You just tricked me! 8-) Variables are scoped quite tightly in XSLT, and between our 2.0.0 build and current D9/D10 builds we've cleaned up our error handling that checks variables for scope. Thus while Xalan may have handled this stylesheet in the past, that was a bug, and we're now doing the proper thing in reporting the error, since the variable isn't in scope at the second reference at Bugzilla3489.xsl; Line#: 269; Column#: 97. (Scope being fairly tightly lexically defined; see the XSLT spec 11.5)
