Eclipse Community Forums: Epsilon » Rule reach and extension consistency in Flock and ETL

Help

Home

Home » Modeling » Epsilon » Rule reach and extension consistency in Flock and ETL

Show: Today's Messages :: Show Polls :: Message Navigator

Rule reach and extension consistency in Flock and ETL [message #1131287]

Thu, 10 October 2013 07:39

Horacio Hoyos
Messages: 146
Registered: October 2009

Senior Member

Hi Everyone,

I hope this post creates an interesting discussion around the subject.

It might be too late (and surely break all the current Flock scripts out there), but for consistency (at least with ETL) the semantics of rule reach and extension in Flock should work the other way round, so migrate rules should:

1. Be "not greedy" by default (hence there should be a greedy annotation and not a strict)
2. Not inherit by default, so u will need an extends keyword and possibly an abstract annotation (if you want to skip instances of super-types from being migrated)

It would be nice to hear ideas/experience regarding this topic Very Happy

Regards,

Horacio Hoyos Rodriguez
EngD Student
University Of York

Report message to a moderator

Re: Rule reach and extension consistency in Flock and ETL [message #1131911 is a reply to message #1131287]

Thu, 10 October 2013 18:05

Dimitris Kolovos
Messages: 659
Registered: July 2009

Senior Member

Hi Horacio,

I can see the benefits of making these changes but I agree with Louis that overhauling the default semantics of the language at this point is probably not an option. One option for a future version of Flock could be to provide a runtime flag that inverts the default semantics.

Cheers,
Dimitris

Report message to a moderator

Previous Topic:	Iterator in an attribute
Next Topic:	[Eugenia] Diagram partitioning

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Mar 09 16:14:21 EDT 2014