Subject: Re: [xsl] value of variable inside a condition doesn't work? From: Mike Brown <mike@xxxxxxxx> Date: Tue, 28 Jan 2003 14:35:02 -0700 (MST) |
S Woodside wrote: > It's so wonderfully backwards. Whoever thought of a variable that > contains a choose statement? :-) Backwards, pshaw! XSLT is a declarative language. You aren't instructing something to name a memory location 'x' and then store value 'y' in it; you're asserting that there is a identical relationship between 'x' and 'y', period. It's just like math. In XML, the element/content hiearchy makes expressing such relationships a matter of containment: <x><y/></x>. <y/> can be written as <xsl:foo/> because an XSLT instruction is a type of function; it can be used interchangably with its evaluated result, since f(x)=y: f of x *is* y. So I'm curious... which XSLT processors cache and don't lazily evaluate extension functions? And aren't extension elements, in theory, in the same boat? (If no one knows what I'm talking about, never mind...) Mike -- Mike J. Brown | http://skew.org/~mike/resume/ Denver, CO, USA | http://skew.org/xml/ XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] value of variable inside , S Woodside | Thread | Re: [xsl] value of variable inside , Tobias Reif |
Re: XSL frustration (was: Re: [xsl], J.Pietschmann | Date | [xsl] background-image question, Koes, Derrick |
Month |