[Bug 8253] [XSLT 2.1] Allow xsl:variable before xsl:param

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8253





--- Comment #6 from Mukul Gandhi <gandhi.mukul@gmail.com>  2009-11-10 12:52:36 ---
(In reply to comment #5)
> >I think this would be something that would not hurt the language.
> 
> My initial feeling is that there's nothing intrinsically wrong with the idea -
> it wouldn't hurt - but I'm not sure it would benefit enough people to be worth
> doing. Obviously, the WG will look at it and make a decision.

In the first post, it was suggested that a capability like following is needed:

<xsl:template name="blah">
  <xsl:param name="param0" />
  <xsl:variable name="tempVar" select="$param0/a/long[@expr]" />
  <xsl:param name="param1" select="$tempVar[1]" />
  <xsl:param name="param2" select="$tempVar[2]" />
</xsl:template>

But as per the XSLT 2.0 spec, the contents of xsl:template can be as follows:

(xsl:param*, sequence-constructor)

I don't think, a change like as suggested should be added to the langauge, as
it corrupts the basic design of a subroutine. For this particular thread, I am
referring to xsl:template as a subroutine.

Subroutine structures are fairly standard, and XSLT seems to be no different in
this regard. The basic essence of certain structures need to be preserved
(here, that's a subroutine :( ).

As suggested by the user, an easy workaround is possible for this particular
need. I don't think a facility should be added to the language, unless there is
strong demand from a large group of users.

I think, a facility like this can be added as an extension to XSLT processors.
But I don't think, it should be added to the main language :(

But if the XSL WG chooses to add this facility to the main XSLT language, users
cannot do much about it :)

Regards,
Mukul


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 10 November 2009 12:52:45 UTC