W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2006

[Bug 1804] [FS] editorial: E.1.4.2 Erases

From: <bugzilla@wiggum.w3.org>
Date: Thu, 13 Apr 2006 04:10:21 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1FTt9x-0002nX-06@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1804


jmdyck@ibiblio.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




------- Comment #2 from jmdyck@ibiblio.org  2006-04-13 04:10 -------
(In reply to comment #1)
> 
> #5 Sem / rule 9 / conclusion. Looking at the grammar
> in 2.3.1 Formal values a simple value is indeed a value.

Has the grammar has changed since CR? While it's true that the language
generated by SimpleValue is a subset of the language generated by Value, this
doesn't justify saying that every SimpleValue is a Value. Consider that e.g.,
the language generated by VarName is a subset of the language generated by
NameTest, but you wouldn't say that every VarName is a NameTest. However, this
is mostly beside the point.

The question is, if a judgment form is declared as
    statEnv |- Value1 erases to Value2
then, in judgments of that form, what can appear in the 'Value1' position? The
FS doc isn't so formal as to say, but it seems to me that the only sensible
answer is: phrases that can be derived from the 'Value' non-terminal. Since
Value doesn't derive SimpleValue, I'm saying that
    statEnv |- SimpleValue erases to text { String }
doesn't conform to the declaration of the judgment form.
Received on Thursday, 13 April 2006 04:10:25 UTC

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