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=4016>. 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=4016 Lazy evaluation of variables causes problems when variables are set in global space ------- Additional Comments From [EMAIL PROTECTED] 2001-10-22 13:18 ------- Its not clear to me why why a side-effect of an extension method is at odds with XSLT. From what I could see, this issue wasn't discussed at all in the spec. Many of the extension examples I've seen make use of side-effects in one way or another. I've been using XSLT for awhile now, and still have trouble determining the subtle differences between what is "legitimate" XSLT and what is not. It may be that some of this is due to vagueness in the specs (particularly with respect to extensions). The working definition of "legitimate" that I use is: "Its OK if the processor lets me do it". I'm also not exactly sure what you mean by "optimizing away variables". Could you provide more details on that? Basically what I'm trying to accomplish here is to make use of a pre- initialized opject for a particular class, rather than using only an object constructed with the default constructor when using the "namespace:method" syntax to invoke the method of an object. If there were some other mechanism to accomplish the same thing, I would gladly use it. I had considered this a problem, because the same stylesheet that worked in Xalan 1 was broken in Xalan 2.
