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

[Bug 1625] Static Typing Feature may find a type error that the dynamic evaluaton would miss

From: <bugzilla@wiggum.w3.org>
Date: Thu, 21 Jul 2005 00:18:09 +0000
To: public-qt-comments@w3.org
Message-Id: <E1DvOlN-0001el-M9@wiggum.w3.org>


simeon@us.ibm.com changed:

           What    |Removed                     |Added
             Status|NEW                         |ASSIGNED
            Summary|Static Typing Feature may   |Static Typing Feature may
                   |find a type error that the  |find a type error that the
                   |dynamic evaluation would    |dynamic evaluaton would miss
                   |miss                        |

------- Additional Comments From simeon@us.ibm.com  2005-07-21 00:18 -------
This part of the processing model talks about dynamic errors and type errors
(when the implementation does not perform static typing), which can be still
raised statically if an implementation can detect that the error will
necessarily occur at run time. This is somewhat orthogonal from the issue of
static typing.

This is somewhat editorial here. We may want to replace the following sentence:

A document type has an optional content type. If no content type is given, then
the type is treated as being the wildcard type for documents, i.e., a sequence
of text and element nodes.

By the corresponding sentences taken from the XQuery book:

If the Static Typing Feature is in effect, all type errors are detected during
static analysis and serve to inhibit the dynamic evaluation phase.

Even though static typing can catch many type errors before an expression is
executed, it is possible for an expression to raise an error during evaluation
that was not detected by static analysis.

- Jerome and Michael
Received on Thursday, 21 July 2005 00:18:14 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:25 UTC