This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1820 - [FS] technical: 4.1.5 Function Calls: dynEnvDefault
Summary: [FS] technical: 4.1.5 Function Calls: dynEnvDefault
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Formal Semantics 1.0 (show other bugs)
Version: Last Call drafts
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Jerome Simeon
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-28 02:11 UTC by Michael Dyck
Modified: 2005-09-27 08:30 UTC (History)
0 users

See Also:

Attachments

Description Michael Dyck 2005-07-28 02:11:01 UTC 
4.1.5 Function Calls

DEv / rule (1|2)
"dynEnvDefault + varValue( Variable1 => Value1'; ...) |- Expr => Value'"
    This won't work, because dynEnvDefault doesn't have entries for the
    variables and functions defined in the Prolog. Instead of
    dynEnvDefault, you should have the dynEnv resulting from
        dynEnvDefault |- PrologDeclList =>dyn dynEnv
    For library modules, this is "stored" in the =>module_dynEnv relation,
    so rule 2 has an easy fix:
        s/dynEnvDefault/dynEnv1/
    However, rule 1 does not appear to have a similar easy fix.
Comment 1 Jerome Simeon 2005-09-06 15:33:17 UTC 
I agree. This is a big bug actually. I think the fix for library modules make
sense. I think we should have something that also records the context for the
prolog for the main module.

Maybe a notation of the form:

#MAIN =>module_statEnv statEnv

would do the trick.

- Jerome
Comment 2 Jerome Simeon 2005-09-27 08:30:02 UTC 
The XSLT and XML Query working groups have adopted the resolution sketched in
comment #1.
Best,
- Jerome