Saxon

I have raised a W3C bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=30283 against the test suite. (This is something of a formality since there is no active WG to consider the bug, but it allows me to fix the relevant tests and link the fix to the bug report).

I have revised test message-0001 so it actually does what was intended, outputting an attribute node in xsl:message. The test succeeds, in that the transformation does not fail, however the Saxon code is written (in class MessageAdapter) to inject a processing instruction node to represent the attribute value, and this is not being output as intended (instead the output is a blank message).

I have revised test message-0404 (which does an integer divide by zero while evaluating the xsl:message content) so that (a) the test is XSLT 3.0 only, and (b) it no longer permits the transformation to fail. I have fixed the Saxon implementation of xsl:message on the 9.8 and trunk branches so it recovers from a dynamic error evaluating the message content and outputs instead a message indicating the error that occurred, following which the transformation continues normally.

The try/catch introduced in comment #3 also fixes the original subject of the bug entry: an xsl:message outputting a function item no longer causes an error. I am adding tests that output a function reference, a map, and an array.

I have further changed the code so that MessageAdapter formats a map or function item using the Err.depict() method used for diagnostic output. This works better in 9.9 than in 9.8, but it still gives some indication of the content which is preferable to an error message.