Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] XSLT 2.1: ElementTest against several names?

From: Florent Georges <lists@------------>
To:
Date: 12/1/2008 1:18:00 PM
Michael Kay wrote:

> Yes, but I think that in any language, you can't expect a type
> to be a completely precise assertion about the set of values that
> you will accept.
> For example, in Java, you can't say "I will accept an Integer or
> a String".

  But there are a lot of stuff in Java I don't want in XSLT ;-)  And
why not, it could be useful, maybe?

> You have to declare your type as the nearest named type in your
> type hierarchy, and rely on explicit parameter validation to
> make a more precise test.

  That's not how I see it for XSLT, but ok, that's consistent.

> I don't think that arguments about the economics of purchasing
> the software are likely to carry much weight.

  PS: That's certainly not an argument of mine.  I am convinced the
purchase is worth its price.  But anyway, there could be several
reasons for SA to be not available.

  Regards,

-- 
Florent Georges
http://www.fgeorges.org/


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent