 |
|
|
Michael Kay wrote:
In one place the "." slipped into the
code instead of "$Arg", and the template operated on the
original text node instead of the partly processed one.
This is one advantage of xsl:function over xsl:template - it prevents
inadvertent use of expressions referring to the context node.
Very interesting point you make there, Michael. I always found it a miss
of the specification that functions cannot act on the current node (yet
I did see that it would have some non-trivial complications in terms of
scope and manageability). From this point of view the motivation of that
decision is much clearer.
Cheers,
-- Abel --
|
|
| |
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.
| |
| |
|
|
|
