On Thu, Jan 8, 2009 at 4:17 AM, Michael Kay <mike(_at_)saxonica(_dot_)com>
wrote:
My first thoughts are that XSLT should raise an error on this, and if Saxon
isn't raising an error then it's a bug. But I need to investigate a bit more
deeply.
If this is a bug, I think I found it accidentally :)
Though I find Saxon's implementation about this to be reasonable (may
be we need to add some explanation to the XPath 2.0 spec inline with
Saxon's implementation).
According to me, casting (promoting) a double to float is a reasonable
operation. The only problem is, that double values larger than 32 bit
(which is the size of float) cannot be represented in a float value
space, and there will be significant loss of information. Saxon
produces the value INF as a result of this cast operation.
--
Regards,
Mukul Gandhi
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--