Stéphane Ducasse wrote: > > No it should follow well specified rules. Ultimately the compiler is not really compiling smalltalk, it is compiling some primitive concepts that Behaviour and friends turn in to smalltalk by virtue of their implementation. There is nothing stopping anyone one defining another language with entirely different conventions. So the compiler should not enforce smalltalk rules. If Behaviour/ClassDescription wants to enforce some rules then that is Behaviour's business and it should be overrideable. > Else this is the mess. > In Smalltalk uppercase are for global variables and lowercase for > private. > Class instance variables are only accessible from the metaclass > methods so they should be > lowercase. > > Now if a lousy compiler allows them this is the problem. > > Not at all, there are times when you might want an instance variable to have an uppercase name. These kind of bending of the rules are particularly useful when using Smalltalk as a DSL. It is only a convention so I do not think that the compiler should enforce it.
Keith _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
