Project

Profile

Help

Bug #6209 ยป Re_ [Saxon - Support #6209] (Closed) Saxon functions not available via function-lookup() in module loaded via load-xquery-module() - 2023-10-01T14_45_12Z.eml

Mary Holstege, 2023-10-01 16:45

 
X-He-Spam-Score: -3.7
Return-Path: <holstege@mathling.com>
Delivered-To: dropbox@plan.io
Received: from m.launch.gmbh ([127.0.0.1])
by m.launch.gmbh with LMTP id YOclLuqFGWXPWAAAJzdhvw
for <dropbox@plan.io>; Sun, 01 Oct 2023 16:44:58 +0200
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on m.launch.gmbh
X-Spam-Level:
X-Spam-Status: No, score=-3.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,DMARC_NONE,HTML_MESSAGE,NICE_REPLY_A,
RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,
RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS autolearn=ham
autolearn_force=no version=3.4.2
X-Spam-Report:
* 1.3 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in
* bl.spamcop.net
* [Blocked - see <https://www.spamcop.net/bl.shtml?23.83.212.10>]
* -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at
* https://www.dnswl.org/, no trust
* [23.83.212.10 listed in list.dnswl.org]
* -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
* [score: 0.0000]
* 0.1 DMARC_NONE DMARC record not found
* -0.1 SPF_PASS SPF check passed
* -0.0 RCVD_IN_MSPIKE_H3 RBL: Good reputation (+3)
* [23.83.212.10 listed in wl.mailspike.net]
* 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record
* 0.0 HTML_MESSAGE BODY: HTML included in message
* -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
* author's domain
* -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
* 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily
* valid
* -0.0 RCVD_IN_MSPIKE_WL Mailspike good senders
* -3.1 NICE_REPLY_A Looks like a legit reply (A)
X-Spam-Score: -3.7
Envelope-to: inbox+saxonica+f38e+saxon@plan.io
Authentication-Results: m.launch.gmbh; dmarc=none (p=none dis=none) header.from=mathling.com
Authentication-Results: m.launch.gmbh; spf=pass smtp.mailfrom=holstege@mathling.com
Authentication-Results: m.launch.gmbh;
dkim=pass (2048-bit key; unprotected) header.d=mathling.com header.i=@mathling.com header.b="mm+TOm9K";
dkim-atps=neutral
Received: from barb.elm.relay.mailchannels.net (barb.elm.relay.mailchannels.net [23.83.212.10])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by m.launch.gmbh (Postfix) with ESMTPS id BE31B80413
for <inbox+saxonica+f38e+saxon@plan.io>; Sun, 1 Oct 2023 16:44:57 +0200 (CEST)
X-Sender-Id: a2hosting|x-authuser|holstege@mathling.com
Received: from relay.mailchannels.net (localhost [127.0.0.1])
by relay.mailchannels.net (Postfix) with ESMTP id B44B17617D8
for <inbox+saxonica+f38e+saxon@plan.io>; Sun, 1 Oct 2023 14:44:54 +0000 (UTC)
Received: from az1-ss103.a2hosting.com (unknown [127.0.0.6])
(Authenticated sender: a2hosting)
by relay.mailchannels.net (Postfix) with ESMTPA id 437557615B4
for <inbox+saxonica+f38e+saxon@plan.io>; Sun, 1 Oct 2023 14:44:54 +0000 (UTC)
ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1696171494; a=rsa-sha256;
cv=none;
b=3AD3b2WwfV0jDyrCa3gjxsOen6WVptTaSV0hAh5lbtlfXPSNNxH7hU5q9utELmd1Var/61
1Hui+cEfaTVcvaJY93BmAwkH16h98aSiefu2wbHvqpUV8by14mnL7so5/1x3F+opzcpIw1
1kIZwd+kPNzh+r0olI16rKpdlPGJdwamhezu0P9+Cb8kPfVDIzDLSQtwbnEWNUGWBsgGZ8
7zXaubuQLv/jsL6bnuZJyehNUY7oFMPioPQ+cWObgS2tyuQkNp6q34eZWZfKohizhsLWq/
MSmlTCpHper1fv8Ku5Bg/1skXACSe9HQ2xzN0BupAQ7SXNljsBhaWimCvsLmEg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;
d=mailchannels.net;
s=arc-2022; t=1696171494;
h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
to:to:cc:mime-version:mime-version:content-type:content-type:
in-reply-to:in-reply-to:references:references:dkim-signature;
bh=mGnPcFw8wShY/0RzM9Cv8soXvSd1djar3fGzcoGYlxA=;
b=8FPGFPVrcfJ9ThVYwzUzOVRp6CVyh7c/UVksqlHqJdbDv1S7WR3tQE8f61bsl9x79zDDTk
jCYqbpS2ytF4447TxN1+ftEIR8dEEm1LghETCxJiA2sKQGmX4DSLgPFzY7kM8cLhauTiyj
1tFWCiigfH+5vy5KHFqnb7Ytzg1uXUnuCXOYPXeHf/J4mL3IRllkARQfxGBdzRd/NE5gAn
W1+6/GBKKqDiyAFjbmgHNTy4Xl5okfJxf+xu2SmJDLWqBj4hxRVmoGxIe3oP3+ddSU2SPU
ocYbtfZOKMpU/J3N0rApmXLLkFX6egaS2h/JesMprDF/h0zteSG4HakbWQOwCQ==
ARC-Authentication-Results: i=1;
rspamd-7c449d4847-5d6nx;
auth=pass smtp.auth=a2hosting smtp.mailfrom=holstege@mathling.com
X-Sender-Id: a2hosting|x-authuser|holstege@mathling.com
X-MC-Relay: Junk
X-MailChannels-SenderId: a2hosting|x-authuser|holstege@mathling.com
X-MailChannels-Auth-Id: a2hosting
X-Wipe-Little: 11c319a9230438b8_1696171494564_1130751364
X-MC-Loop-Signature: 1696171494564:3173335833
X-MC-Ingress-Time: 1696171494563
Received: from az1-ss103.a2hosting.com (az1-ss103.a2hosting.com
[68.66.226.123])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384)
by 100.104.112.135 (trex/6.9.1);
Sun, 01 Oct 2023 14:44:54 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=mathling.com; s=default; h=In-Reply-To:From:References:To:Subject:
MIME-Version:Date:Message-ID:Content-Type:Sender:Reply-To:Cc:
Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:
Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:
List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
bh=mGnPcFw8wShY/0RzM9Cv8soXvSd1djar3fGzcoGYlxA=; b=mm+TOm9K9IVRgb0BNb0B36MOi0
vgGDfIBfw9snzSEJKuy9WVevzNfO9DccCC06hFSXlNKedz1TaCmxq3Z1L4cvgBBv+hcvCz6dyikbu
SXUeIHVfo6v5C0Kr5vYbMx0HbteXEKIouAH13KgydirOo9itpNumNRchhISvYKP4u7ILQcCDcG+xs
Ibb5aN6qdtmPOvKG9ZMteFAsxg0V+/afEWwk93VUo0jojvP2bjjLwJ9gkg2IZiNNpSOG3CONxieJp
m5FZPbR51fatUE1ZzaGPUus2v2GBDUjQC6j77x93hmIIa6+gniMhNzFOK/PRs87KDhhcU+TSpHs5y
aVqr7SkA==;
Received: from 107-130-101-52.lightspeed.sntcca.sbcglobal.net ([107.130.101.52]:58970 helo=[192.168.86.32])
by az1-ss103.a2hosting.com with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256
(Exim 4.96)
(envelope-from <holstege@mathling.com>)
id 1qmxgj-009Wsp-28
for inbox+saxonica+f38e+saxon@plan.io;
Sun, 01 Oct 2023 07:44:53 -0700
Content-Type: multipart/alternative;
boundary="------------g3FbA9XO89YqS0S0bmexYn2x"
Message-ID: <3ddf2412-7147-546e-f3fe-86876e7d693b@mathling.com>
Date: Sun, 1 Oct 2023 07:44:53 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.10.0
Subject: Re: [Saxon - Support #6209] (Closed) Saxon functions not available
via function-lookup() in module loaded via load-xquery-module()
Content-Language: en-US
To: Saxonica Developer Community <inbox+saxonica+f38e+saxon@plan.io>
References: <redmine.issue-6209.20230926204639.3872@plan.io>
<redmine.journal-24780.20230930223701.3872@plan.io>
From: Mary Holstege <holstege@mathling.com>
In-Reply-To: <redmine.journal-24780.20230930223701.3872@plan.io>
X-AuthUser: holstege@mathling.com

This is a multi-part message in MIME format.
--------------g3FbA9XO89YqS0S0bmexYn2x
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

I respect your decision, although don't you think it is strange that
lookup-function() cannot even find built-in F&O functions just because
it is called from within a function loaded with load-xquery-module?
Seems that the context has been modified: to truncate it in a weird way.

On 9/30/23 15:37, Saxonica Developer Community wrote:
>
> --- In your reply, please do not write below this line ---
>
> Issue #6209 <https://saxonica.plan.io/issues/6209?pn=1#change-24780>
> has been updated by Michael Kay.
> ------------------------------------------------------------------------
>
> * *Tracker* changed from /Bug/ to /Support/
> * *Status* changed from /New/ to /Closed/
> * *Assignee* set to /Michael Kay/
>
> I'm closing this with no action: |load-|query-module` is not intended
> to modify the static or dynamic context. I've proposed a clarification
> in the 4.0 specification.
>
> ------------------------------------------------------------------------
>
>
> Support #6209: Saxon functions not available via function-lookup()
> in module loaded via load-xquery-module()
> <https://saxonica.plan.io/issues/6209?pn=1#change-24780> closed
>
> * *Author: *Mary Holstege
> * *Status: *Closed
> * *Priority: *Low
> * *Assignee: *Michael Kay
> * *Start date: *2023-09-26
> * *Applies to branch: *12
>
> I have a module where the call to a Saxon function is encapsulated via
> function-lookup() (portability)
>
> When I call the encapsulated function directly, it works. If I call
> the Saxon function directly, it works. But if I load the module via
> load-xquery-module() then the function-lookup() fails even though the
> direct call works. The function here is saxon:xquery FWIW, although I
> don't believe that matters.
>
> Attached code has all four cases: direct.xqy just imports the module
> and calls things; indirect.xqy uses load-xquery-module() and then
> tries to call things.
>
> saxon.sh direct.xqy saxon.sh indirect.xqy
>
> (with appropriate mods to paths in saxon.sh and config.xml)
>
> Files bug20230926.zip
> <https://saxonica.plan.io/attachments/download/64354/bug20230926.zip>
> (2.88 KB)
>
> ------------------------------------------------------------------------
>
> You have received this notification because you have either subscribed
> to or are involved in a project on Saxonica Developer Community site.
> To change your notification preferences, please click here:
> https://saxonica.plan.io/my/account?tour=mail_preferences
> <https://saxonica.plan.io/my/account?tour=mail_preferences>
>
>
> This notification was cheerfully delivered by <https://plan.io/>
> Planio <https://plan.io/>
>
--------------g3FbA9XO89YqS0S0bmexYn2x
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I respect your decision, although don't you think it is strange
that lookup-function() cannot even find built-in F&amp;O functions
just because it is called from within a function loaded with
load-xquery-module? Seems that the context has been modified: to
truncate it in a weird way.<br>
</p>
<div class="moz-cite-prefix">On 9/30/23 15:37, Saxonica Developer
Community wrote:<br>
</div>
<blockquote type="cite"
cite="mid:redmine.journal-24780.20230930223701.3872@plan.io">
<!--[if !mso]><!-- -->
<link href="https://assets.plan.io/stylesheets/fonts.css"
rel="stylesheet" type="text/css">
<!--<![endif]-->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style>a:link{color:#0088b7}a:visited{color:#0088b7}a:hover{color:#0088b7}a:active{color:#0088b7}</style>
<table class="planio_mail"
style="border-collapse:collapse;margin-bottom:1em;border:1px
solid
#bbb;padding:4px;border-spacing:0;margin-bottom:0;width:100%;border:none;padding:0"
width="100%" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td class="planio_mail header" style="border:1px solid
#bbb;padding:4px;text-align:center;width:100%;font-family:MarketWeb,
Helvetica, Arial,
sans-serif;font-size:0.8em;color:#D7D7D7;border:none;padding:0">
<p>--- In your reply, please do not write below this line
---</p>
</td>
</tr>
<tr>
<td class="planio_mail" style="border:1px solid
#bbb;padding:4px;border:none;padding:0">Issue <a
href="https://saxonica.plan.io/issues/6209?pn=1#change-24780"
style="color:#0088b7" moz-do-not-send="true">#6209</a>
has been updated by Michael Kay.
<hr
style="width:100%;height:1px;background:#ccc;border:0;margin:1.2em
0">
<ul class="journal details"
style="color:#959595;margin-bottom:1.5em">
<li><strong>Tracker</strong> changed from <i>Bug</i> to
<i>Support</i></li>
<li><strong>Status</strong> changed from <i>New</i> to
<i>Closed</i></li>
<li><strong>Assignee</strong> set to <i>Michael Kay</i></li>
</ul>
<p>I'm closing this with no action: <code
style="font-family:Hack, Consolas, Menlo,
&quot;Liberation Mono&quot;, Courier,
monospace;font-size:85%;background-color:#ececec;word-wrap:break-word;border-radius:3px;padding:0.2em;margin:0">load-</code>query-module`
is not intended to modify the static or dynamic context.
I've proposed a clarification in the 4.0 specification.</p>
<hr
style="width:100%;height:1px;background:#ccc;border:0;margin:1.2em
0">
<h1 style="font-family:&quot;ProximaNova-Bold&quot;,
Helvetica, Arial,
sans-serif;font-weight:normal;margin:0px;font-size:1.3em;line-height:1.4em">
<a
href="https://saxonica.plan.io/issues/6209?pn=1#change-24780"
style="color:#0088b7;text-decoration:none"
moz-do-not-send="true">Support #6209: Saxon functions
not available via function-lookup() in module loaded
via load-xquery-module()</a> <span class="badge
badge-status-closed"
style="position:relative;font-weight:bold;font-size:10px;bottom:2px;padding:1px
3px;margin-right:2px;margin-left:2px;border-radius:2px;text-transform:uppercase;text-decoration:none;color:#1D781D;border:1px
solid #1D781D">closed</span>
</h1>
<ul class="details"
style="color:#959595;margin-bottom:1.5em">
<li><strong>Author: </strong>Mary Holstege</li>
<li><strong>Status: </strong>Closed</li>
<li><strong>Priority: </strong>Low</li>
<li><strong>Assignee: </strong>Michael Kay</li>
<li><strong>Start date: </strong>2023-09-26</li>
<li><strong>Applies to branch: </strong>12</li>
</ul>
<p>I have a module where the call to a Saxon function is
encapsulated via function-lookup() (portability)</p>
<p>When I call the encapsulated function directly, it
works. If I call the Saxon function directly, it works.
But if I load the module via load-xquery-module() then
the function-lookup() fails even though the direct call
works. The function here is saxon:xquery FWIW, although
I don't believe that matters.</p>
<p>Attached code has all four cases: direct.xqy just
imports the module and calls things; indirect.xqy uses
load-xquery-module() and then tries to call things.</p>
<p>saxon.sh direct.xqy
saxon.sh indirect.xqy</p>
<p>(with appropriate mods to paths in saxon.sh and
config.xml)</p>
<fieldset class="attachments" style="border:solid
#ccc;border-width:1px 0 0 0"><legend>Files</legend> <a
href="https://saxonica.plan.io/attachments/download/64354/bug20230926.zip"
style="color:#0088b7" moz-do-not-send="true">bug20230926.zip</a>
(2.88 KB)<br>
</fieldset>
<div itemscope="itemscope"
itemtype="http://schema.org/EmailMessage">
<div itemscope="itemscope" itemprop="action"
itemtype="http://schema.org/ViewAction">
<link itemprop="url"
href="https://saxonica.plan.io/issues/6209?pn=1#change-24780">
<meta itemprop="name" content="View Issue">
</div>
<meta itemprop="description" content="View this issue
update on Planio">
</div>
</td>
</tr>
<tr>
<td class="planio_mail footer" style="border:1px solid
#bbb;padding:4px;font-size:0.8em;width:100%;border:none;padding:0">
<hr
style="width:100%;height:1px;background:#ccc;border:0;margin:1.2em
0">
<p>You have received this notification because you have
either subscribed to or are involved in a project on
Saxonica Developer Community site.
To change your notification preferences, please click
here: <a
href="https://saxonica.plan.io/my/account?tour=mail_preferences"
class="external moz-txt-link-freetext"
style="color:#0088b7" moz-do-not-send="true">https://saxonica.plan.io/my/account?tour=mail_preferences</a></p>
</td>
</tr>
<tr>
<td class="planio_mail planio_footer" style="border:1px
solid
#bbb;padding:4px;text-align:center;width:100%;font-family:MarketWeb,
Helvetica, Arial,
sans-serif;font-size:1.2em;color:#D7D7D7;border:none;padding:0"><br>
<div><a href="https://plan.io/"
style="color:#0088b7;color:#D7D7D7;text-decoration:none"
moz-do-not-send="true">This notification was
cheerfully delivered by</a></div>
</td>
</tr>
<tr>
<td class="planio_mail planio_footer_logo" style="border:1px
solid
#bbb;padding:4px;text-align:center;width:100%;border:none;padding:0"><a
href="https://plan.io/" title="Planio"
style="color:#0088b7" moz-do-not-send="true"><img
src="https://assets.plan.io/images/planio_logo_gray_204x50.png"
alt="Planio" style="vertical-align:middle;border:none"
moz-do-not-send="true" width="102" height="25"
border="0"></a></td>
</tr>
</tbody>
</table>
</blockquote>
</body>
</html>

--------------g3FbA9XO89YqS0S0bmexYn2x--
    (1-1/1)