On 6 oct. 2010, at 23:28, Alexandre Bergel wrote:
Hi!
I bumped into this:
DSMCell>>configurationForNamespace
self accesses: (self from mooseModel sourceLanguage = #Smalltalk ... -=-=-=-=-=-=-=-=-=
'self from mooseModel' may return nil.
This happens when I open a DSM on the following object: group := FAMIXNamespaceGroup new. group add: (FAMIXNamespace new name: 'name1'); add: (FAMIXNamespace new name: 'name2'); add: (FAMIXNamespace new name: 'name3').
DSM is apparently making an assumptions on the object it gets.
Well, all tools make such assumptions, especially that they have some non-empty models. The problem here is that we expect to have a moosemodel. I changed the test to create a moosemodel instead of a group.
Next failure comes from the DistributionMap wizard: same thing, it assumes that the model is not "empty" as it is above so it works fine in real cases.
#possibleElementSelectors returns an empty collection in this case. Cyrille, could you just add check for non-empty collection?
Cheers, Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
I don't understand where I should put this check ?
2010/10/7 Simon Denier Simon.Denier@inria.fr
On 6 oct. 2010, at 23:28, Alexandre Bergel wrote:
Hi!
I bumped into this:
DSMCell>>configurationForNamespace
self accesses: (self from mooseModel sourceLanguage = #Smalltalk ...-=-=-=-=-=-=-=-=-=
'self from mooseModel' may return nil.
This happens when I open a DSM on the following object: group := FAMIXNamespaceGroup new. group add: (FAMIXNamespace new name: 'name1'); add: (FAMIXNamespace new name: 'name2'); add: (FAMIXNamespace new name: 'name3').
DSM is apparently making an assumptions on the object it gets.
Well, all tools make such assumptions, especially that they have some non-empty models. The problem here is that we expect to have a moosemodel. I changed the test to create a moosemodel instead of a group.
Next failure comes from the DistributionMap wizard: same thing, it assumes that the model is not "empty" as it is above so it works fine in real cases.
#possibleElementSelectors returns an empty collection in this case. Cyrille, could you just add check for non-empty collection?
Cheers, Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I change the strategy.
Instead of ConfigurationForPackage, I created configurationForSmalltalkPackage, where we consider that we have a Smalltalk architecture. -> this is necessary for cook. And, instead of configurationForNamespace, I created configurationForJavaNamespace, where we consider the namespaces come from java.
Now, you can compute a DSM on packages or Namespaces without model.
Cheers, Jannik
On Oct 7, 2010, at 16:29 , Cyrille Delaunay wrote:
I don't understand where I should put this check ?
2010/10/7 Simon Denier Simon.Denier@inria.fr
On 6 oct. 2010, at 23:28, Alexandre Bergel wrote:
Hi!
I bumped into this:
DSMCell>>configurationForNamespace
self accesses: (self from mooseModel sourceLanguage = #Smalltalk ...-=-=-=-=-=-=-=-=-=
'self from mooseModel' may return nil.
This happens when I open a DSM on the following object: group := FAMIXNamespaceGroup new. group add: (FAMIXNamespace new name: 'name1'); add: (FAMIXNamespace new name: 'name2'); add: (FAMIXNamespace new name: 'name3').
DSM is apparently making an assumptions on the object it gets.
Well, all tools make such assumptions, especially that they have some non-empty models. The problem here is that we expect to have a moosemodel. I changed the test to create a moosemodel instead of a group.
Next failure comes from the DistributionMap wizard: same thing, it assumes that the model is not "empty" as it is above so it works fine in real cases.
#possibleElementSelectors returns an empty collection in this case. Cyrille, could you just add check for non-empty collection?
Cheers, Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--- Jannik Laval
-
Cyrille Delaunay -
Laval Jannik -
Simon Denier