testInstanceAndClassSideWhenMergingClassAndMetaclass
| node | node := self model entityNamed: #'Root::Smalltalk::ReferenceModel::TheRoot'. self assert: (self model entityNamed: #'Root::Smalltalk::ReferenceModel::TheRoot_class' ifAbsent: [nil]) isNil. self assert: node instanceSide == node. self assert: node classSide == nil.
nil or node ?
I would prefer node so that we get a circular situation
Stef
Without thinking through all implications, me also.
In the long term, I'd favor to model "sides" of classes as some first level entity ... introducing "group side" als die Dritte im Bunde. But that is for a future FAMIX extension package.
AA
On 23 Nov 2007, at 21:34 , stephane ducasse wrote:
testInstanceAndClassSideWhenMergingClassAndMetaclass
| node | node := self model entityNamed: #'Root::Smalltalk::ReferenceModel::TheRoot'. self assert: (self model entityNamed: #'Root::Smalltalk::ReferenceModel::TheRoot_class' ifAbsent: [nil]) isNil. self assert: node instanceSide == node. self assert: node classSide == nil.
nil or node ?
I would prefer node so that we get a circular situation
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
not clear to me but for now I will make sure that I get node instead of nil
On 23 nov. 07, at 21:39, Adrian Kuhn wrote:
Without thinking through all implications, me also.
In the long term, I'd favor to model "sides" of classes as some first level entity ... introducing "group side" als die Dritte im Bunde. But that is for a future FAMIX extension package.
AA
On 23 Nov 2007, at 21:34 , stephane ducasse wrote:
testInstanceAndClassSideWhenMergingClassAndMetaclass
| node | node := self model entityNamed: #'Root::Smalltalk::ReferenceModel::TheRoot'. self assert: (self model entityNamed: #'Root::Smalltalk::ReferenceModel::TheRoot_class' ifAbsent: [nil]) isNil. self assert: node instanceSide == node. self assert: node classSide == nil.
nil or node ?
I would prefer node so that we get a circular situation
Stef _______________________________________________ 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
Is there a menu option to do this merging? ^^
AA
On 23 Nov 2007, at 21:34 , stephane ducasse wrote:
testInstanceAndClassSideWhenMergingClassAndMetaclass
| node | node := self model entityNamed: #'Root::Smalltalk::ReferenceModel::TheRoot'. self assert: (self model entityNamed: #'Root::Smalltalk::ReferenceModel::TheRoot_class' ifAbsent: [nil]) isNil. self assert: node instanceSide == node. self assert: node classSide == nil.
nil or node ?
I would prefer node so that we get a circular situation
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
importingContext mergeClassAndMetaclass
importingContext should....
importingContext distinguish....
Stef On 23 nov. 07, at 22:40, Adrian Kuhn wrote:
Is there a menu option to do this merging? ^^
AA
On 23 Nov 2007, at 21:34 , stephane ducasse wrote:
testInstanceAndClassSideWhenMergingClassAndMetaclass
| node | node := self model entityNamed: #'Root::Smalltalk::ReferenceModel::TheRoot'. self assert: (self model entityNamed: #'Root::Smalltalk::ReferenceModel::TheRoot_class' ifAbsent: [nil]) isNil. self assert: node instanceSide == node. self assert: node classSide == nil.
nil or node ?
I would prefer node so that we get a circular situation
Stef _______________________________________________ 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