as Anne said, FMMultivalueLink is for * multiplicity and 1 in the other side. To limit memory usage you can use the Null version of this one so it will be automatically replaced by the regular version if one element is added. MultiMulti is for *-* associations so you have to instantiate one in each side.
<derived> is for things that don't require to be stored in the .mse for example because you can derive it (compute) from other datas.
I think there is a chapter in the Moose book but not sure it is really helpful
2016-07-01 17:09 GMT+02:00 Anne Etien anne.etien@univ-lille1.fr:
Hi,
We asked for an engineer to modify it. We do not know yet if we got it or not.
What I do is that I use the example of Famix for ST to create my own FAMIX. <mutivalued> means that the maximal multiplicity is *. In that case, you need FMMultiValueLink. But when you want to initiate one FMMultivalueLink to null, you create a FMNullMultiValueLink. I don’t really know when there is <derived> or not.
Anne
Le 1 juil. 2016 à 16:47, Alexandre Bergel alexandre.bergel@me.com a écrit :
hi
Is there at least a bit of documentation about Fame? I am trying to meta-describes some C elements, but it is very difficult. All these are very mysterious: FMNullMultivalueLink, FMMultivalueLink FMMultiMultivalueLink
<multivalued> <derived>
I feel Fame is very powerful, but very hard to understand.
Alexandre
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev