W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2009

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

From: <bugzilla@wiggum.w3.org>
Date: Tue, 10 Nov 2009 03:24:26 +0000
To: public-qt-comments@w3.org
Message-Id: <E1N7hLG-0006iO-3x@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8253


Mukul Gandhi <gandhi.mukul@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gandhi.mukul@gmail.com




--- Comment #1 from Mukul Gandhi <gandhi.mukul@gmail.com>  2009-11-10 03:24:25 ---
(In reply to comment #0)

Personally speaking, I think something like this is not needed in an
xs:template definition.

According to me, xsl:template is something like a subroutine or a method as in
other programming languages. Ofcourse, a subroutine in languages like OO
languages are a bit different than xsl:template's in XSLT, from execution point
of view.

The most prevalent syntax of subroutines (here, xsl:template is similar to a
subroutine) is the subroutine name, subroutine parameters and return type.

I don't think, an existence of variable between xsl:template parameters is a
good design choice.

A workaround like, another parameter should be ok, but certainly a variable
between xsl:param's doesn't look good to me. 

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 03:24:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:29 UTC