search

abreslav-from-google-code / abreslav

Automatically exported from code.google.com/p/abreslav
0 stars 0 forks source link

Don't generate MapClasses when transforming AST to Model #28

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
If we generate MapClass action when transforming TransformationAS to 
Transformation (assuming we have some information about what classes to 
map), there actions would be fixed and when someone runs the 
transformation (stored as a model) after changing the input model which 
does not affect the transformation correctness, he just will have some of 
his classes skipped.

The idea is the following:
1. Don't generate MapClass actions
2. Store a reference to an input model in the Transformation object
3. Refer mapped classes by prototype (not by MapClass instance)

4. When executing transformation, simply map all the classes from the 
input model, except for those which are explicitly skipped (by SkipAction)

Original issue reported on code.google.com by eja...@gmail.com on 19 Mar 2007 at 6:08