Writing a message to stderr is surely just a specific example of an
application-level function?  What if my XSLT processor has a GUI or
Web interface and there is no "stderr"?  In that case I want a callback 
into the application code, with the callback being able to optionally
raise 
an exception for the XSLT processor.

I would think that the extension mechanism is where one would deal with 
this situation.

Steve Ball


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list