8 Nov
2008
8 Nov
'08
9:01 a.m.
On Nov 7, 2008, at 8:42 PM, Alexandre Bergel wrote:
Maybe there is something I misunderstood. Merging classes and
metaclasses when importing means that one single class will represent
both the class and its metaclass I guess.
Yes
As far as I can see, an analysis may depend on whether
you merge
classes and metaclasses.
It seems hard to imagine than any analysis should be depend on
whether
there is such a merging.
you mean independent?
If we have the same data represented the same way independently of
merging
we favor that an analysis code does have to have different cases
based
on merging
or not? This means that there will be twice less classes in a
model.
It is already like that since two years you can ask whether you want
to merge or not.
A system
complexity view on a imported (using merging) smalltalk application
will be different than the one with no merging.
Of course so what? It depends what you want to see.
When you look at packages dependency it makes sense to merge,
No?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev