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

[Bug 24549] Primed stylesheets, execution scope and stability of functions

From: <bugzilla@jessica.w3.org>
Date: Thu, 13 Feb 2014 09:42:56 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-24549-523-RWugdUEEFq@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24549

C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |cmsmcq@blackmesatech.com
         Resolution|---                         |FIXED

--- Comment #1 from C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> ---
We discussed this in Prague.  In reviewing the section to get a sense of the
context, we noticed a couple of points not directly relevant to this bug
report:

- The note in the first bullet item of 2.3.2 is not quite right; it has now
been arranged that no two packages can declare stylesheet parameters with the
same name.  (Or so we now believe.)

- Paragraph 2 in bullet item 2 is not quite wrong, but feels misleading:  the
context item for the initialization of global variables and parameters is not
the initial context item but its root.  The "use" of the initial context item
for initialization of global variables is thus rather indirect.

On the point initially raised here:  the reference to 'all' functions is too
broad, as the point does not apply to unstable functions.  Possible fix:  for
"all functions" read "deterministic functions". Or "... creates an execution
scope.  As defined elsewhere, this has as a consequence that deterministic
functions called within that execution scope with the same arguments will
return the same results.")

When we followed the link to F and O, we discovered that it does not explicitly
connect identity of execution scope to the expectation that deterministic
functions will return identical results for identical arguments (need to insert
"within a given execution scope" before "repeated calls with the same explicit
and implicit arguments must return identical results"?).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 13 February 2014 09:42:57 UTC

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