RE: RFC XSLT Standard -"Further support for variable /

>> 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.

I believe you can do this in Java as well using the reflection API, though it is somewhat of a pain.

Rick



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