Experiment on defining concepts by generator about famix

[jecisc]

The problem if you stop using precooked entity is how you manage code of something managing not one MM but multiple.

Exemple:
How do you build the File and Folder generator?

Currently, it check in the current MM which entity is a FamixTFile and a FamixTFolder to know what to generate.

I we don't have this information, how do we do this generator?

[sbragagnolo]

But nor file or folder are language specific concepts. Maybe OS specific, but we do not really care.
If you define it at the level of the visitor you can allways subclass this visitor, sharing the same definition.

[sbragagnolo]

Also if the visitor delegates to a strategy, you can always reuse the same strategy, and that's it .

[badetitou]

I believe we need to keep pre-cooked entity.
Maybe they are not all defined because they mostlty come from legacy famix, but still.

However, I believe we can split the trait in different packages.
Famix-Anchor-Traits (TFile)
Famix-OO-Traits (TClass)
Famix-General-Traits (TNamed)

[badetitou]

Note that this is something we are already doing with FileBasedMetamodelGenerator

[badetitou]

Please consider this issue #115

[NicolasAnquetil]

note: linked to #113