[XSL-LIST Mailing List Archive Home]
[Reply To This Message]
Re: dynamic-context type-branching
Subject: Re: dynamic-context type-branching|
From: ac <ac@xxxxxxxxxxxxx>
Date: Tue, 05 Feb 2008 17:53:52 -0500
Another use case that we have is when an application/stylesheet supports
user variables to hold content and values used repeatatively, for
example, and where the variable/expression evaluator may typically
output different types, depending on the variable/context being evaluated.
I picked the saxon:evaluate() use case because it seemed obvious that
anything could come out of it, but I also have one or two other cases
where a template/function can output different things, typically a
string or a node sequence. All these cases seem to be more
concentrated around content query and layout management, where
polymorphism contributes to content abstraction. I would certainly
support increased orthogonality in handling atomic values, in node
selecting/processing contexts (ex: apply-templates).
Michael Kay a icrit :
In schema unaware xslt2 environments, what would be the best way to
select action depending on the result type (ex: string, text
node(s), attribute(s), element(s)) of saxon:evaluate(), ex:
I think it's basically to do an xsl:choose. However, your note
to add "apply-templates on atomic values" to the candidate
for future XSLT versions. It's a little hard to come up with really
convincing use cases, but I think it would make the language more
and that's always a good thing. Certainly, polymorphism on atomic
well as on nodes seems intrinsically desirable.
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format