W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2016

[Bug 29858] [XP31] Named Function References - context information

From: <bugzilla@jessica.w3.org>
Date: Thu, 22 Sep 2016 16:35:49 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29858-523-7WJrBmM73p@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29858

Michael Dyck <jmdyck@ibiblio.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jmdyck@ibiblio.org

--- Comment #1 from Michael Dyck <jmdyck@ibiblio.org> ---
Two things, both picky:

(1)
"[Definition: A named function reference is an expression that evaluates to a
function."

While that statement is true, there are other expressions that evaluate to a
function, so it isn't very good as a definition of 'named function reference'.
To get a statement that's true *only* for named function references, we could
add something like "by literally specifying the function's name and arity".
(Though it sounds a bit clunky.)

Really, a named function reference is, by definition, just an instance of the
NamedFunctionRef nonterminal. If we were more willing to use nonterminals in
prose, "named function reference" wouldn't even need to exist as a term.


(2)
"The name and arity of the function reference must correspond to a function
signature found in the static context of the expression and to a function found
in the *function names* component of the dynamic context.]"

That's a normative requirement, which we don't usually put into definitions.
(Skimming through the glossary, I see that the definitions of 'encoding
declaration' and 'zero-digit' also contain requirements.)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 22 September 2016 16:36:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:02 UTC