Hi Gregor,
thanks for updating the interpreter.
Regarding your comment: It is not about expressiveness -- I believe
all current units can be reduced to ConditionalUnits, except for
AmalgamationUnits (see some of my old e-mails). It's more the fact
that most users want to implement a While-Loop rather than a
For-Loop (with a fixed count) and it is not really intuitive why one
should use a "CountedUnit" for that...
Cheers,
Christian
On 01/10/2012 07:19 PM, Gregor Bonifer wrote:
By the
way. The model still is semantically redundant. A LoopUnit can be
easily simulated using a ConditionalUnit and an empty Rule as
shown in simLoop.png. The execution is fundamentaly different but
the observable behaviour is undistinguishable. I also added an
example how to construct a CountedUnit recursively using a trivial
helper model. The current count is passed to the repeated unit as
parameter.
Regards,
Gregor
Am 10.01.2012 16:24, schrieb Gregor Bonifer:
Done.
Regards,
Gregor
Am 10.01.2012 16:04, schrieb Christian Krause:
Gregor,
could you maybe update the interpreter so that it supports
LoopUnits? Should be a matter of 2 minutes I guess.
Cheers,
Christian
On 01/08/2012 10:05 AM, Enrico Biermann wrote:
Hello,
I support the removal of counted and its replacement loop
unit. Though
the editors should support a shortcut for creating a
sequential unit
with 20 times the same rule. Maybe changing the editor
commands from
"Creation of counted unit with x" to "Creation of sequential
unit with x
times the rule" is sufficient.
Regards,
Enrico
On 07.01.2012 20:14, Christian Krause wrote:
Hi,
I know I said that we should stick with the model changes
that we have
so far, but there is one thing that is bugging me and I
would like to
use the opportunity to change the Henshin model at one
more place.
CountedUnits with positive count can be directly modeled
using
SequentialUnits (correct me if I'm wrong). The only
interesting case
is when the count value is negative, which should have a
"loop as long
as possible" semantics. Since this is the only interesting
case, I
suggest that we remove CountedUnit from the model and add
a LoopUnit,
which behaves like a CountedUnit with a negative count
value.
Please comment / vote.
Cheers,
Christian
PS: Felix, if you are concerned about the extra work that
is necessary
for the migration code, I can support you there.
_______________________________________________
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
_______________________________________________
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
|