Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] Getting WordprocessingML p style

From: Florent Georges <darkman_spam@-------->
To:
Date: 2/2/2007 8:42:00 PM
David Carlisle wrote:

  Hi

> It isn't just the cardinality rules that are different,
> the way comparing values of different types are handled
> differs as well, with = being more lenient than eq (and
> even more lenient in backward compatibilty mode).

  Yes I know.  And I know that when I write either eq or =.
But I like to allow just the "lenientness" I need.  Just the
genericity I need.  Because it is that, when comparing two
atomic values, = is more generic, it accepts more values to
be compared than eq.

  I need compiler and runtime help to detect my errors as
soon as possible.

  For example, when I have to compare an untyped value taken
from a node to an integer, I will use eq and xs:integer().
More to type, but more checks.  Until I know I need instead
to be lenient.

  But I need more help than you from the compiler ;-)

> Generally speaking I find the = behaviour more natural,
> and easier to type (which is an important consideration:-)

  :-)

  Regards,

--drkm



















	

	
		
___________________________________________________________________________ 
Dicouvrez une nouvelle fagon d'obtenir des riponses ` toutes vos questions ! 
Profitez des connaissances, des opinions et des expiriences des internautes sur Yahoo! Questions/Riponses 
http://fr.answers.yahoo.com


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