> As Mariano writes, most applications implement a message #isAbstract > themselves with the exact semantics they require. I don't think a > generic message in Behavior is really useful, especially if it is not > used by the core system.
In that case, we could have isAbstractClass or something else. I feel this information is important. > If the class > contains any method that sends #subclassResponsibility, the we > consider the class as abstract. I am not sure what "contains" means in that context. But apparently, the definition you gave is not sufficient. The presence of subclassResponsibility need to be checked in the methods obtained from superclasses. (the code I gave in my previous email does not satisfy this although). I will create an issue. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
