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 11681 - semantics of non-deterministic expressions
Summary: semantics of non-deterministic expressions
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3.0 (show other bugs)
Version: Member-only Editors Drafts
Hardware: Macintosh Mac System 9.x
: P2 normal
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-06 17:14 UTC by Daniela Florescu
Modified: 2011-02-05 22:28 UTC (History)
3 users (show)

See Also:

Attachments

Description Daniela Florescu 2011-01-06 17:14:03 UTC 
While discussing bug 
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11352
during the discussion the following question was raised.

What is the semantics in XQuery 3.0 of the following program:
==

declare %nondeterministic function read-line() as xs:string external;

(read-line(), read-line(), read-line)

==
Are we guaranteed to read the lines in order, or not ?

In other words, does XQuery 3.0 impose an order of execution of subexpressions ?

I think determining the answer to this question is a pre-requisite
to solving bug #11352.
Comment 1 Andrew Eisenberg 2011-01-10 23:38:18 UTC 
In XQuery 3.0, 2.3.4 Errors and Optimization, we say:

"An implementation is always free to evaluate the operands of an operator in any order."
Comment 2 Jim Melton 2011-02-05 22:28:08 UTC 
This bug was resolved by the action taken in Bugzilla Bug #11352.  As a result, I have marked it RESOLVED/FIXED.  Because you were present for the discussion and agreed, I'm also marking it CLOSED.