Michael Kay wrote:
On 29/02/2012 16:19, Michael Kay wrote:
On 29/02/2012 15:32, Andrew Welch wrote:
Or in 3.0
<xsl:sequence select="$numbers!xs:integer(.)"/>
Was there an issue with $numbers/xs:integer(.) ?
There were people who weren't prepared to countenance @price/2 = 2
Whoops. That's already true in XPath 2.0, and it doesn't seem
to have caused any nuclear accidents yet.
If I remember well the discussions in the WG, the main obstacle was the
relationship with the document ordering semantics of the '/' operator. What
for instance if $numbers is a heterogenous sequence of nodes and strings? (for
atomic values-only sequences, it could have been easily defined as stable
though)
Regards,
--
Florent Georges
http://fgeorges.org/
http://h2oconsulting.be/
--~------------------------------------------------------------------
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>
--~--