You don't need to subclass, you can also use extensionHi,
I'm getting acquainted more with Moose and FAMIX and I am not really sure how to proceed (mostly due to lack of documentation and link rot).
What I want to do is add "multiplicity" attribute to FAMIXAttribute.Now I see an option:1) create a subclass of FAMIXAttribute
yes, two ways of doing it:2) add a method.. something likeFAMIXAttribute>>multiplicity<MSEProperty: #multiplicity type: #MyFAMIXMultiplicity>^ multiplicity
now Moose can generate models from smalltalk source code and I would like to infer this information.
For example for types, there is MooseImportingContext>>computeTypeOfAttributesSo I'm assuming I would have to do something similar.
yes, you can change the importer or post process the model as said above
And finally, if I want to help the importer and actually write that information into the source code, I would have to add another pragma there... something likeMyClass>>myAttribute<MSEMultiplicity: '2..*' type: MyType>^ myAttribute
and then modify the smalltalk importer to be able to recognize this and produce MyFAMIXAttribute instead of the default one.
Am I on the right track? Should it be done differently?
Any pointers appreciated,Peter
_______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev