- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 24 Jan 2008 08:23:04 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5288 ------- Comment #6 from tim@cbcl.co.uk 2008-01-24 08:23 ------- I agree with Mike. I think that XPST00005 error is the sort of thing a compiler might warn a user about during compilation rather than it actually being a fatal error. I find it particularly annoying that it means that the behaviour changes depending on whether or not static typing is switched on. I also agree with Michael regarding the type of fn:error. I rather like the way Haskell approaches exceptions in a functional language. I've found there's rather a lot to be learned from Haskell, particularly with regard to handling side-effects in a functional setting. Without breaking existing implementations, might a change be made which states that an implementation may raise XPST00005 but is not required to do so?
Received on Thursday, 24 January 2008 08:23:12 UTC