I wanted to address the following issue
Look for senders of:
propertySignature <property: #XXX longName: 'YYY' description: 'ZZZ'>
And replace with:
propertySignature <MSEProperty: #propertySignature type: #Number> <MSEComment: 'ZZZ'>
but I do not understand it :(
numberOfMessageSends <property: #MSG longName: 'Number of message sends' description: 'The number of message from a method'> ^self lookUpPropertyNamed: #MSG computedAs: [self mooseModel isSmalltalk ifTrue: [| parser | parser := VisualWorksParseTreeMetricCalculator new. parser processMethod: self usingImporter: nil inModel: nil. parser numberOfMessageSends] ifFalse: [-1]]
numberOfMessageSends <MSEProperty: #numberOfMessageSends <MSEComment: 'Number of message sends' description: 'The number of message from a method'> ^self lookUpPropertyNamed: #MSG computedAs: [self mooseModel isSmalltalk ifTrue: [| parser | parser := VisualWorksParseTreeMetricCalculator new. parser processMethod: self usingImporter: nil inModel: nil. parser numberOfMessageSends] ifFalse: [-1]]
How does the system know after that the property is linked with #MSG if MSG is not part <property: #MSG longName: 'Number of message sends' description: 'The number of message from a method'>
Why do we duplicate the method selector?
why do we create comment as a separate entity. To me it looks like we are looking for complicated queries after. I still do know how I can get a method containing two tags in one query.
What is the rationale? Why having a comment directly in would be a bad idea.
So guess what? I will wait because fixing the 122 left.
Stef