[Moose-dev] Re: about <MSEProperty: #propertySignature type: #Number> <MSEComment: 'ZZZ'>

Hi Stef, First, the pragma should be: <MSEproperty: #afferentCoupling type: #Number> It's like an identifier in code. Then the only thing different here is what will be saved in the MSE file. So, instead of AFFC, we will have afferentCoupling. The only real problem is in the case where we rely on looking up the property in the dictionary before trying to compute it. Let me give you an example: FAMIXBehavioralEntity>>numberOfLinesOfCode <MSEProperty: #numberOfLinesOfCode type: #Number> <MSEComment: 'The number of lines of code in a method.'> ^ self lookUpPropertyNamed: #LOC computedAs: [...] In this case, there is a mismatch between what gets looked up in the implementation (#LOC), and what is described (#numberOfLinesOfCode). This is because the current external parsers export the LOC property, but when we are inside Moose, we want to see numberOfLinesOfCode (it reads better, and it scales better given that we tend to have a tone of metrics and acronyms become confusing). So, after loading a model with LOC properties from MSE, by default, these will get stored in the properties dictionary. Now, we still have the problem that after we save the model and load it again, we will lose the LOC information because now it will be stored with the numberOfLinesOfCode. So, until we fix the external parsers, we can have the following workaround: FAMIXBehavioralEntity>>numberOfLinesOfCode <MSEProperty: #numberOfLinesOfCode type: #Number> <MSEComment: 'The number of lines of code in a method.'> ^ self privateState propertyAt: #LOC ifAbsentPut: [ "this is to make sure we get #LOC" self privateState propertyAt: #numberOfLinesOfCode ifAbsentPut: [ "this is to deal with the Moose #numberOfLinesOfCode" ...] ] Cheers, Doru On 19 Sep 2011, at 19:40, Stéphane Ducasse wrote: -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."