Hello hani,
I was discussing with roel and we came up with the conclusion that we are losing information with your approach. You are changing the meaning of what a stub is. Been a stub means that you are a reference outside of the model.
Note that been stub was introduced to support fragile importer (some tools like Sniff+ lost information and you get a class without an attribute and accesses to it but no attribute, so the attribute is a stub).
- If there is an inheritance definition to a class that is not in the model, the inheritance definition is not a stub since it is in the model and may be one class is not.
- You can get a method that is not imported but referenced and it is a stub because of the same problem. A method is not a stub because it is in a stub class. A method is a stub because at the end of the import phase it was not imported but referenced.
I suggest that you define another property for encoding what you want: called it impactedByStub or inContactOfStub.
Stef
On Aug 8, 2008, at 6:21 PM, Hani ABDEEN wrote:
new version of Moose Development
FAMIXMethod>>isStub
isStub "a fAMIXMethod is stub if it is declared as stub or if it belongs to a stub class"
^super isStub or: [self belongsTo isStub]. _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev