 |
|
|
mark4asp wrote:
> if ($date > @entryDate) then
> set $date = @entryDate
XSLT variables are single-assignment. You need to use two separate
variable names, or turn the problem inside out and do the conditional
inside the computation of the variable's value. Which makes most sense
depends on the details of your stylesheet.
Conditionals: depending on what you're doing, the xsl:if or xsl:choose
directives may be the right answer
(http://www.w3.org/TR/xslt#section-Conditional-Processing), or you may
want a predicate test inside an XPath expression
(http://www.w3.org/TR/xpath#predicates). Again, which makes most sense
depends on the details of your stylesheet.
> Finally, Does it make sense to use variable types in xsl, such as
> integers, datetime, etc., or is everything a string?
In XSLT 1.0, everything is a string until converted in the expression.
In XSLT 2.0 and XQuery, types become more meaningful.
--
Joe Kesselman / Beware the fury of a patient man. -- John Dryden
|
|
| |
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.
| |
| |
|
|
|
