resolveTemp crashes the ATL module [message #1120568] |
Sun, 29 September 2013 19:22 |
Leonardo Montecchi Messages: 10 Registered: September 2013 |
Junior Member |
|
|
Hello,
I'm trying to use the resolveTemp function within an ATL module. However, I'm experiencing a very strange behavior:
When calling
thisModule.resolveTemp(v, 'name');
...
If NO rule exists for 'v' creating an object named 'name', then the function is executed and returns OclUndefined, as it should
If such rule exists, then the ATL module creashes: the execution is interrupted (with not exceptions on the console) and the output file is not generated at all.
Coult you please help me, or point to some direction? I'm calling
thisModule.resolveTemp(e, 'detected').debug();
from the "do" part of a MatchedRule, and the resolveTemp is supposed to reference another MatchedRule... so it should be the right place within the module.
Thanks.
Leonardo Montecchi
Instituto de Computação, UNICAMP
http://ic.unicamp.br/~leonardo
http://laser.ic.unicamp.br/
|
|
|
|
Re: resolveTemp crashes the ATL module [message #1123457 is a reply to message #1122366] |
Wed, 02 October 2013 15:31 |
Leonardo Montecchi Messages: 10 Registered: September 2013 |
Junior Member |
|
|
Hello,
thanks for your answer.
It took me a while to figure out how to do the same thing within regular matched rules, but it is possible, thanks for your suggestion.
It actually works if called from another rule, in the declarative section.
That is, instead of calling resolveTemp in rule A for finding element X of rule B, I call it in rule B for finding element Y of rule A.
However the module still crashes if I add the .debug() operation:
target <- thisModule.resolveTemp(e.refImmediateComposite(),'reset'),
--OK
target <- thisModule.resolveTemp(e.refImmediateComposite(),'reset').debug(),
--Crashes (with no visible hints)
Best regards,
Leonardo Montecchi
Instituto de Computação, UNICAMP
http://ic.unicamp.br/~leonardo
http://laser.ic.unicamp.br/
|
|
|
|
Powered by
FUDForum. Page generated in 0.04049 seconds