Hi Guys, Why don't you do something more focused on the long term and don't you change the Smalltalk compiler with namespaces?

I don't think it should be that hard since each class already belongs to a category. Each category could instead be a dictionary from where the compiler could find classes that are mentioned in the class source. This has worked wonders in Java (classes inside packages). This way classes' names can be repeated ad eternum without generating collisions or otherwise polluting excessively the name space. So for example: FAMIXAssociation subclass: #FAMIXInvocation instanceVariableNames: 'sender receiver receiverSourceCode signature candidates' classVariableNames: '' poolDictionaries: '' category: 'Famix-Core' Would be instead: Association subclass: #Invocation instanceVariableNames: 'sender receiver receiverSourceCode signature candidates' classVariableNames: '' poolDictionaries: '' category: #FamixCore Then the category would be an index in the SystemDictionary: SystemDictionary at: #FamixCore put: Category new. (SystemDictionary at: #FamixCore) belongingClassList add: #Invocation "this should be done automatically by the subclass: method above" (SystemDictionary at: #FamixCore) referencedClassList add: ... "classes that are referenced by classes belonging to category #FamixCore" What do you think? Cheers, Guillermo. Message: 1 Date: Mon, 27 Sep 2010 22:00:33 +0200 From: Tudor Girba <tudor.girba(a)gmail.com> Subject: [Moose-dev] Re: Class renaming in Moose Algos Graph To: Moose-related development <moose-dev(a)iam.unibe.ch> Message-ID: <C912A83B-6BDC-4775-AC26-CE2DBC5540AE(a)gmail.com> Content-Type: text/plain; charset=us-ascii Hi Simon, These classes should be called MAlgo (or MAL ?). I started to do that a while ago, but apparently I forgot to commit this change. Cheers, Doru On 27 Sep 2010, at 19:42, Simon Denier wrote: _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev