|
|
Re: [ATL] Transformation termination and confluence [message #494343 is a reply to message #494214] |
Fri, 30 October 2009 07:04   |
Eclipse User |
|
|
|
William, thanks for the link, however there actually is no useful information. How does stages relate to termination/confluence - rules could be matched forever meaning no termination, because matched source patterns are not removed from further pattern application. This is logical conclusion by reading that link.
Is double pushout (DPO) or single pushout (SPO) approach used for transformations? How does confluence achieved (which by simple words mean, that rules can be applied in different order producing the same result, i.e. transforming the same source model ATL produces the same target model even if transformation rule application order is unique in each run)? what assumptions let apply rules in a non-deterministic way (declarative execution mode) and to produce the same result (this is confluence )? is this a result of late initialization of target patterns? if so, how circular (mutual) dependencies are avoided?
I understand, that not every ATL user is familiar with these topics, but I am sure, that termination/confluence should been addressed by developing declarative transformation execution mode. May better informed to shed more light?
|
|
|
|
Powered by
FUDForum. Page generated in 0.03429 seconds