Stef is right. The only kind of class extension that can be easily
packaged is method addition and override, sadly.
Cheers,
Alexandre
On 27 Apr 2010, at 21:16, Johan Fabry wrote:
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
[email protected] - http://dcc.uchile.cl/~jfabry
PLEIAD Lab - Computer Science Department (DCC) - University of Chile
_______________________________________________
Pharo-users mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
