W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2014

[Bug 26958] On not precluding updates in XQuery 3.1

From: <bugzilla@jessica.w3.org>
Date: Tue, 04 Nov 2014 21:45:09 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-26958-523-EfMoMfQJt4@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26958

--- Comment #19 from Jonathan Robie <jonathan.robie@gmail.com> ---
(In reply to C. M. Sperberg-McQueen from comment #18)
> With respect to comment 16, I do not think the argument "the text already
> does X, therefore we should not entertain objections to the text doing X" is
> a sound one, even if the text does in fact do X.

Huh?  I think the argument is more along these lines:

A. "I don't think we should be required to change the text to do X"
B. "But the text already does X"

> All of the occurrences of 'Creates a new map ...' and similar could easily
> be replaced, without loss of clarity, by 'Returns a map ...' or 'Evaluates
> to a map ...'.  In the case where the map passed in as an argument is
> deep-equal() to the map returned, the current wording can (as JR points out)
> be read as dictating the creation of a new map rather than potentially
> returning the same map (assuming that maps have intensional identity and not
> extensional identity).

Whatever wording we use, we need to know the result of the kinds of queries I
provided in comment #16. I don't think we have to change the wording
significantly to do so, but I do think we need this level of clarity if we want
to know the results of existing functions and operations defined in our
language.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 4 November 2014 21:45:11 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:59 UTC