W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2010

[Bug 9916] New: Allow patterns to access template parameters

From: <bugzilla@jessica.w3.org>
Date: Fri, 11 Jun 2010 22:49:03 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-9916-523@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9916

           Summary: Allow patterns to access template parameters
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 2.1
        AssignedTo: mike@saxonica.com
        ReportedBy: evan@evanlenz.net
         QAContact: public-qt-comments@w3.org


It would be really useful if patterns could have access to template parameters.

The parameter would still have to be declared by the template for it to be
visible (as with tunnel parameters). Also, when visible, it would shadow any
global variables with the same name (just as with local variables/parameters).

For example:

<xsl:template match="*[. is $node]">
  <xsl:param name="node" tunnel="yes"/>
  <found/>
</xsl:template>

<xsl:template match="*">
  <not-found/>
</xsl:template>

Right now I have to use <xsl:choose> (yuck).

I can't think of any issues with this other than the somewhat unintuitive
aspect of the parameter being declared just below where it's being referenced
(as opposed to above).

-- 
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 Friday, 11 June 2010 22:49:04 UTC

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