| Refactoring transformation by seprating into modules [message #1096347] |
Wed, 28 August 2013 05:03  |
Cuauhtemoc Castellanos Messages: 8 Registered: September 2012 Location: paris |
Junior Member |
|
|
Hi,
I am refactoring some transformations of mine, and I am trying to separate some inherited rules into 2 distinct modules.
example:
the initial module
module M
abstract rule absA
rule A1 extends absA
rule A2 extends absA
The separation into 2 distinct modules
module M1
abstract rule absA
rule A1 extends absA
and
module M2
abstract rule absA
rule A2 extends absA
Finally I superimpose module M1 and M2 at runtime.
My questions are the followings:
In this superimposition order, does A1 extends absA of module M1 or module M2?
Is this separation in to module the same as the one module transformation?
Thank you for your help in advance.
|
|
|
| Re: Refactoring transformation by seprating into modules [message #1096353 is a reply to message #1096347] |
Wed, 28 August 2013 05:13   |
Hugo Bruneliere Messages: 560 Registered: July 2009 |
Senior Member |
|
|
Hello,
Generally, the result depends on whether you superimpose M1 on M2 or M2 on M1.
In your specific case, both situations should work similarly: considering that both absA rules are similar in the two ATL modules, erasing one by another should not change the final behavior of your composed transformation.
If you need more insights on this superimposition mechanism, you can refer to the dedicated section of the ATL guide.
Best regards,
------------------------------------------
Hugo Bruneliere - R&D Engineer
AtlanMod research team (Inria, EMN & LINA)
Ecole des Mines de Nantes
Nantes - France
------------------------------------------
|
|
|
|
|
Powered by
FUDForum. Page generated in 1.63143 seconds