Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


[xsl] "Higher Order Functions for XQuery" -- static context and focus

From: Florent Georges <lists@--------.--->
To: XSL Mulberry list <xsl-list@-----.------------.--->
Date: 9/4/2009 9:34:00 AM
  Hi,

  I guess this is a good place to discuss John's proposal for
"Higher Order Functions for XQuery."  Sorry if it is not.

  In the section "1.2 Inline Functions", the fifth paragraph is
<http://snelson.org.uk/~jpcs/higher-order-functions.html#inline-func>:

    The static context for the function body is inherited from
    the location of the inline function expression, with the
    exception of the static type of the focus (context item,
    context position, and context size) which is undefined.

  I am not sure to understand what does "the static type of the
focus" mean.  The focus is a component of the dynamic context,
and I am not sure "type" is used here as in the rest of the RECs.

  BTW, is this restriction really relevant?  A user can anyway
reference those values by using intermediary variables:

    let $i := position()
      return
        function() { $i }

and the processor would be able to detect whether the function
body does use any component of the focus, to see if it has to
save those as well or not.

  I guess I missed the point behind this choice.  Any idea?

  Regards,

-- 
Florent Georges
http://www.fgeorges.org/





















      


--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe@l...>
--~--



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent