Re: The Perils of Sudden Type-Safety in XPath 2.0
now suddenly make Saxon crash with ClassCastException! I mean, come on, isn't it obvious that when I want to create a text node that that object behind the variable is turned into a string somehow? Even Java does that automatically!
<xsl:if test="$x and not($x='')">
than now raises and error that xs:object supposedly doesn't compare with xs:string! Get real! The xs:object in this case actually happens to be a java.lang.String! I mean, how close can you get?
Finally things now work just differently, I continue to get crashes and stuff not terminating, and who knows what other bad things are happening.
I now revert back to Saxon 7.3, this is killing me. I really applaud Michael for his Saxon work, but this sudden move to (needless) strict type checking without a way for migration was a bad idea. Will I be forever stuck with Saxon 7.3?
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format