Hi Christian, Hi all,
I support the proposal of Christian as it provides a clear and
intuitive way to specify input and output parameters.
Best regards,
Frank
On 10/31/2014 8:58 AM, Christian Krause
wrote:
Hi,
Since this topic already came up in the discussion, here is one proposal
for a refined parameter concept:
The Parameter class gets two boolean flags: "input" and "output". If the
input flag is set the parameter value must be provided by the user (if not
the engine throws an exception). If the input flag is not set it will be
matched by the engine. The engine would similarly provide only output
Parameters back to the application. Parameters which are neither input nor
output are internal variables. And of course it is also possible to have
in+out params.
The only worry I have is that when we introduce this change we will break
existing transformations.
What do you think?
Cheers,
Christian
_______________________________________________
henshin-dev mailing list
henshin-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/henshin-dev
--
________________________________________________________________________
Dr. Frank Hermann
________________________________________________________________________
Research Associate at SnT frank.hermann@xxxxxx
+352 466644 5864 www.securityandtrust.lu
Postal address Visiting address
--------------------------------- ---------------------------------
securityandtrust.lu
University of Luxembourg D104, Campus Kirchberg
4, rue Alphonse Weicker 4, rue Alphonse Weicker
L-2721 Luxembourg L-2721 Luxembourg
________________________________________________________________________