16447 2012-03-20 14:40:01 +0000 Inheritance loop 2012-03-31 21:14:50 +0000 1 1 1 Unclassified WebAppsWG WebIDL unspecified PC All RESOLVED INVALID P2 normal --- 1 w3c cam mike public-script-coord public-webapps-bugzilla oldest_to_newest 65830 0 w3c 2012-03-20 14:40:01 +0000 The following is a statement of fact (drop "MUST NOT" and say "can't"): An exception must not be declared such that its inheritance hierarchy has a cycle. That is, an interface A cannot inherit from itself, nor can it inherit from another interface B that inherits from A, and so on. The inheritance loop check needs to be performed during binding (it is redundant to say MUST here). 65895 1 w3c 2012-03-21 12:10:07 +0000 I've thought a bit more about this one... keep it. But the algorithm in the binding section needs to take this requirement into consideration! I.e., binding needs to have error handling defined, if it doesn't already. And I don't think it currently does. 65930 2 cam 2012-03-21 22:56:22 +0000 Do you mean the requirements for the prototype property in #es-interfaces needs to handle invalid IDL like interface A : B { }; interface B : A { }; ? I don't think we really need to. It's clearly an error, and we don't want implementors to deal with the problem in some way, we want the specs to be fixed. :) 66314 3 w3c 2012-03-31 21:14:50 +0000 ok, fair enough. Easy enough to fix later if it comes up as an issue.