Hi Christian,
in order to not break existing transformations, we could use
three-valued Enum attributes instead of boolean flags, with the
values "true", "false" and "neutral". "neutral" would be the
default value.
The issue I see is how to support this in the graphical editor. We
really haven't found a nice concept yet. One idea is to assign
keywords to the parameter names in the comma-seperated list, which
effectively bloats up the rules in width. Another idea is to use
several compartments for the different parameter types, which
bloats up in the rules in height.
Regards,
Daniel
Am 31.10.2014 08:58, schrieb Christian Krause:
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
--
Dipl.-Inf. Daniel Strüber
Software Engineering Research Group
Philipps-Universität Marburg, Germany, Hans-Meerwein-Str., Room 05D12
Phone: +49-6421-28-21511
