What:
Extend attribute-value-template behavior to include the 'name' attribute for XSP's <xsp:element> and <xsp:attribute>.
Why:
Syntactic sugar, really. We now offer AVT for attribute values in literal output, so, why not have it for the generated names of elements and attributes created via <xsp:element> and <xsp:attribute> to save users a bit of verbosity? Compare,
<xsp:element> <xsp:name><xsp:expr>$perl_expression<xsp:expr></xsp:name>
<!-- contents --> </xsp:element>
vs.
<xsp:element name="{$perl_expression}">
<!-- contents -->
</xsp:element>Incurred Risk:
Well, any edit to the house of cards that is XSP.pm is a risk, IMO, but this is a two-line change. If this RFC gets a +1 I'll add test files as well, just to be sure.
Thoughts?
-kip
