>> The need to have class names comes from using the global namespace: > > (Smalltalk at: ConsistentClass name) == ConsistentClass > > metaclasses is not part of global namespace and therefore don't > required to have some constraints in > while answering #name message. > > Actually, it could answer 'ClassName metaclass' , or just 'a Metaclass' > any form is acceptable.
No what you are saying is dogmatic. So far the metamodel of smalltalk is simple just class, packages does not even exist but as soons as you want to have a way to manipulate classes, you can manipulate metaclass and I do not know you but me I like when I want a class extension on a metaclass that it does not end up on the instance side. > I'd rather punish those, who in own code expecting that metaclasses > should answer something which can be parsed for detecting a class > name! > > >>> >>>> Stef >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [email protected] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [email protected] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
