Traits versus packages
Posted by
jfabry on
Apr 28, 2010; 1:16am
URL: https://forum.world.st/Traits-versus-packages-tp2068491.html
Hi all,
quick question.
Preamble: If I have a trait TAMStructuralZoom defined in the package AspectMaps (for example), and I want to apply it to the class FAMIXNamespace, defined in the package Famix-Core (for example), this implies that I need to change the class definition of FAMIXNamespace like this:
FAMIXScopingEntity subclass: #FAMIXNamespace
uses: TAMStructuralZoom
instanceVariableNames: ''
classVariableNames: ''
poolDictionaries: ''
category: 'Famix-Core'
Question: this change is now part of the Famix-Core package, right? Is it possible for this change to be part of the AspectMaps package? I want this for the obvious modularity & source code management advantages.
--
Johan Fabry
[hidden email] -
http://dcc.uchile.cl/~jfabryPLEIAD Lab - Computer Science Department (DCC) - University of Chile
_______________________________________________
Pharo-users mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users