Altova Mailing List Archives


RE: [xsl] RFC XSLT Standard - "Further support for variable / parameter expansion of XSLT attributes"

From: naha@----------
To:
Date: 3/6/2002 6:27:00 AM
Quoting Michael Kay <michael.h.kay@xxxxxxxxxxxx>:

> 5.1 (xsl:output) is already done in the XSLT 2.0 WD (in fact, it was
> done in
> XSLT 1.1).
> 
> I must admit I thought we had changed xsl:message to allow an AVT (4.1)
> and
> was surprised to discover that we hadn't.
> 
> I think there will be some resistance from members of the WG to
> changing
> those attributes whose values are QNames of objects defined in the
> stylesheet (mode, template name, use attribute sets). Compiled
> languages
> generally don't keep their symbol tables around at run-time. There's
> also
> the problem of keeping namespace declarations around at run-time (though
> the
> key() function sets a precedent).
> 
> It's also hard to think of many languages (COBOL is the only one that
> comes
> to mind) that allow a function or subroutine to be called by supplying
> its
> name as a string.

This is possible in a number of Lisp dialects, but I suppose that doesn't 
surprise anyone.  I don;t know much about FORTH but I'd expect it might
allow this as well.


[...]

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Disclaimer

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.