|
|
Re: EMFTVM: Problem using EDataType objects as parameter of lazy rules [message #1039131 is a reply to message #1038846] |
Thu, 11 April 2013 19:58 |
|
Using primitive data types for rule elements is (currently) not supported in
EMFTVM. It is technically quite possible to add this feature, but there's more
to it than one simple ClassCastException; the trace metamodel is also not
prepared for it. You can file a bug for this if you like.
As a workaround for your specific situation, you can split the lazy rule in
two (booleans only have two possible values), and factor out the common part
in a super-rule using rule inheritance.
Kind regards,
Dennis
Cheers,
Dennis
|
|
|
Re: EMFTVM: Problem using EDataType objects as parameter of lazy rules [message #1039646 is a reply to message #1039131] |
Fri, 12 April 2013 11:54 |
EtienneB Mising name Messages: 35 Registered: June 2011 |
Member |
|
|
Thanks Dennis,
a more systematic workaround is to use "atl called rules", however I am not yet familiar enough with EMFTVM to know if this change (lazy rule --> called rule) has other impacts in terms of execution semantics.
Besides it is interesting to use rules inheritence as you propose since it is a strong contribution of EMFTVM.
I am porting a lot of code from atl to EMFTVM and I am experiencing several important differences.
I will probably create a new thread for discussing these issues, specially since I beleive the new features of EMFTVM are worth making the effort.
Etienne.
[Updated on: Fri, 12 April 2013 12:01] Report message to a moderator
|
|
|
|
Powered by
FUDForum. Page generated in 0.03362 seconds