<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>22878</bug_id>
          
          <creation_ts>2013-08-04 13:40:13 +0000</creation_ts>
          <short_desc>[XSLT 3.0] Compatibility of overriding functions</short_desc>
          <delta_ts>2014-10-24 13:59:36 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>XPath / XQuery / XSLT</product>
          <component>XSLT 3.0</component>
          <version>Working drafts</version>
          <rep_platform>PC</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>CLOSED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Michael Kay">mike</reporter>
          <assigned_to name="Michael Kay">mike</assigned_to>
          
          
          <qa_contact name="Mailing list for public feedback on specs from XSL and XML Query WGs">public-qt-comments</qa_contact>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>91622</commentid>
    <comment_count>0</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2013-08-04 13:40:13 +0000</bug_when>
    <thetext>I think the rules for overriding functions in xsl:override should add the constraints:

(a) if the overridden function has identity-sensitive=&quot;no&quot; then the overriding function must have identity-sensitive=&quot;no&quot;

(b) if the overridden function has override-extension-functions=&quot;no&quot; then the overriding function must have override-extension-functions=&quot;no&quot;.

Justification:

(a) the compiler may make optimizations based on the fact that a function was specified to not be identity-sensitive; for example, it may move function calls out of a loop. Overriding this attribute would invalidate such optimizations.

(b) when the compiler sees override-extension-functions=&quot;no&quot; it should be able to generate a call to an extension function (ignoring the user-defined function) if one is available; since this may usefully involve generating inline code for the extension function, it should not have to reconsider this decision if the user-defined function is overridden in another package.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>93658</commentid>
    <comment_count>1</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2013-09-23 17:13:09 +0000</bug_when>
    <thetext>MK and Abel reviewed this proposal and agreed the change was necessary.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>113698</commentid>
    <comment_count>2</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2014-10-24 13:59:36 +0000</bug_when>
    <thetext>Note that part of this was reverted by a decision on bug #27125</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>