Subject: RE: [xsl] Re: XPath 2.0: Problems with the two boolean constants true and false From: "Michael Kay" <mhk@xxxxxxxxx> Date: Thu, 9 Oct 2003 12:49:40 +0100 |
> The problem is that the boolean value produced by the > template is assigned to an untyped variable (because the > instantiating code is generic and cannot know the type of > values produced by the template it instantiates). This is the bit that I don't understand. You must know something about the values produced by the code you are calling, otherwise the result is meaningless to the caller. What isn't clear to me (though Jeni seems to have divined it in her usual way...) is what kind of contract you want to have between the calling code and the called code. Usually this contract is expressed in terms of types; if you want to express it some other way, then I would like to understand that. Michael Kay XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Re: XPath 2.0: Problems w, Michael Kay | Thread | Re: [xsl] Re: XPath 2.0: Problems w, Jeni Tennison |
RE: [xsl] Re: XPath 2.0: Problems w, Michael Kay | Date | Re: [xsl] Re: XPath 2.0: Problems w, Jeni Tennison |
Month |