eclipse-qvtd-bot
commented
1 week ago By Adolfo Sanchez-Barbudo Herrera on Oct 30, 2016 12:47
Repro:
- Checkout branch cs2as-asanchez/506751 (ocl-master, qvtd-ewillink/miniocl)
- Activate debug in GenerateCS2ASTx.mwe2 [1]
- Execute GenerateCS2ASTx.mwe2
- Inspect generated s_Delphi-r-9-final.graphml [2]
- I see no dependencies between:\ a) m_simpleFactor_ast_designator usimpleFactor_ast (49)\ b) m_factor_ast_expList ufactor_2_DelphiFunctionCallExpression_actualParams (34)
- With these indexes the latter (b)) is incorrectly executed before the former (a))
Corresponding Delphi.ocl code that shows that the dependency is required:
context simpleFactor\ def : ast() : as::astm::Expression =\ self.designator.ast()
context factor\ def : ast() : as::astm::Expression = ...\ else\ if isAFunctionCall()\ then as::astm::DelphiFunctionCallExpression {\ calledFunction = self.designator.ast(), \ actualParams = expList.createActualParams()\ } ...
context cs::exprList -- a helper\ def : createActualParams() : OrderedSet(as::ActualParameterExpression) =\ self.exps->collect(x | \ as::ActualParameterExpression { value = x.ast.oclAsType(as::Expression) } )->asOrderedSet()\ \ The problem is that when execution java code corresponding to x.ast inside the helper, the .ast property has not been computed yet.
As a hint. Something to highlight that may be relevant is that the the mapping source of a) (i.e simpleFactor) is a subtype of the mapping source of b) (i.e factor). Both factor and simpleFactor are instantiable meta-classes. All corresponding AS model elements should be created before factor properties are computed.
| --- | --- | | Bugzilla Link | 506751 | | Status | RESOLVED FIXED | | Importance | P3 normal | | Reported | Oct 30, 2016 12:25 EDT | | Modified | Nov 18, 2016 11:20 EDT | | Blocks | 506328 | | Reporter | Adolfo Sanchez-Barbudo Herrera |
Description
I think the following problem is related to the scheduler. When debugging the transformation, I'm observing an unexpected behaviour from the CGed transformation.
When executing the the method "CACHE_exprList_createActualParams" piece of code (invoked from "MAP_m_factor_ast_expList" mapping), the directly contained "simpleFactor" model element is processed and there is not corresponding AS element associated with it (it is null). This is a suspicious case of incorrectly scheduled rules. The method "MAP_m_simpleFactor_ast_designator" should have been previously invoked.
Repro and more analysis following next, as soon as I get the bugzilla ID.