never thought of this case, but you are absolutely right. As
workround you might wrap the subUnit twice and use those wrappers as
subUnits:
+ ActualSubUnit
+-- X
|
+ SubWrapper1
+-- Param X1
+-- X1 -> X
+-- ActualSubUnit
|
+ SubWrapper2
+-- Param X2
+-- X2 -> X
+-- ActualSubUnit
|
+ SequentialUnit
+-- Param A
+-- Param B
+-- A -> X1
+-- B -> X2
+-- SubWrapper1
+-- SubWrapper2
I think this is pretty bad. We should think of a better solution.
Am 13.01.2012 23:20, schrieb Christian Krause:
Assume you have a sequential unit with parameters A and B in which
another unit with a single parameter X is called twice. The first
time, it should be invoked with A, the second time with B. So I
have to add the following parameter mappings to the sequential
unit:
A -> X
B -> X
But now, when the subunits are invoked, the engine should get into
trouble because it does not know whether to pass A or B for X.
On 01/12/2012 12:53 PM, Stefan Jurack wrote:
Right, analogously to method calls where the caller passes parameters to
and fetches parameters from the callee.
Am 12.01.2012 12:26, schrieb Christian Krause:
Hi,
parameter mappings are managed by the parent transformation unit,
correct?
chhers,
christian
_______________________________________________
henshin-dev mailing list
henshin-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/henshin-dev
_______________________________________________
henshin-dev mailing list
henshin-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/henshin-dev
_______________________________________________
henshin-dev mailing list
henshin-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/henshin-dev
|