[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: The Perils of Sudden Type-Safety in XPath 2.0

Subject: RE: The Perils of Sudden Type-Safety in XPath 2.0
From: "Michael Kay" <michael.h.kay@xxxxxxxxxxxx>
Date: Tue, 18 Feb 2003 20:40:45 -0000
xs object
It looks to me as if your problems are mainly due to interactions
between the new type checking rules, which are defined in the XPath
specs, and Java extension functions, which aren't. It's quite possible
that extension functions need a bit of a rethink as to how they fit into
the 2.0 type system. Just be patient, tell me where the problems are,
and I'll look at them. I've always made it quite clear that Saxon 7.x is
trail-blazing and that it's not intended for the faint-hearted.

Michael Kay
Software AG
home: Michael.H.Kay@xxxxxxxxxxxx
work: Michael.Kay@xxxxxxxxxxxxxx 

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx 
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Gunther Schadow
> Sent: 18 February 2003 18:10
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re:  The Perils of Sudden Type-Safety in XPath 2.0
> 
> 
> Just a few example how much trouble this causes:
> 
> I had:
> 
>    <xsl:value-of select="$x"/>
> 
> 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!
> 
> I had
> 
>    <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?
> 
> -Gunther
> 
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 


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


Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.