- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 13 Sep 2006 20:21:42 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3697 ------- Comment #2 from frans.englich@telia.com 2006-09-13 20:21 ------- One problem with fixing tests, such as these, that violate the static typing feature is that it requires adding XPTY0004 as alternative baseline(if one doesn't decide to rewrite the test, which often spoils the intent with the test). The problem is that XPTY0004 is too wide, an implementation could issue XPTY0004 for a reason that isn't valid and therefore incorrectly pass the test. The proper thing would be to have a specific error code for static typing errors. I believe defining the semantics for that error code is formally possible and reasonable to implement. It would also make static typing behaviors more easy to identify for users. Well, it's a pity such things are realized first now.
Received on Wednesday, 13 September 2006 20:22:13 UTC