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

[Bug 14662] [UPD 3.0] 2.3.2 Updating Annotation Assertion

From: <bugzilla@jessica.w3.org>
Date: Wed, 30 Jul 2014 13:28:17 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-14662-523-9J0hsNj5VQ@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14662

--- Comment #3 from Jonathan Robie <jonathan.robie@gmail.com> ---
In today's meeting, we agreed to allow these three possibilities:

%updating("allowed")
%updating("prohibited")
%updating("required")

e.g.

declare function local:foo($x as %updating("allowed") function())
{

};

declare function local:foo($x as %updating("prohibited") function())
{

};

%updating("allowed") means the same thing as the current %updating function
assertion.  (Note that we need to change the term to "function assertion" in
the update spec.)

The meaning of "prohibited" and "required" is obvious, matching only if the
function is non-updating or updating respectively.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 30 July 2014 13:28:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:47 UTC