- From: Stephen Buxton <Stephen.Buxton@oracle.com>
- Date: 16 Feb 04 11:34:41
- To: public-qt-comments@w3.org
- Cc:
SECTION 2.2.3.2: dynamic evaluation phase Second para, last sentence: "If the Static Typing Feature is not in effect, an implementation is allowed to raise type-related warnings during the static analysis phase, but it must proceed with the dynamic evaluation phase despite these warnings. In this case, type errors must be detected and raised during the dynamic evaluation phase." This sentence makes the Static Typing Feature all-or-nothing, precluding what I will call a partial implementation of the Static Typing Feature, in which an implementation detects and raises some, but not all, type errors, and does not progress to the dynamic evaluation phase if it finds a type error. This does not appear to do the user any good. It means that if the implementation does not do a total job of type error checking, then effectively it has not done any at all (except to raise warnings). I think it would be better to say "if the Static Typing Feature is not in effect, then it is implementation-defined what type errors are detected and raised during the static analysis phase, aborting the dynamic evaluation phase." - Steve B.
Received on Monday, 16 February 2004 14:34:44 UTC