|
Re: [Xcore] specifying a setter for a many-valued derived feature [message #1751791 is a reply to message #1751769] |
Sat, 14 January 2017 05:17 |
Ed Merks Messages: 33137 Registered: July 2009 |
Senior Member |
|
|
Derived setters are really not well tested and given that a multi-valued features never have a generated setter, it doesn't seem so sensible. Also, even for the getter, there are parts of the framework that expect a multi-valued feature's return value to implement InternalEList, so even that part might case problems. You could define an operation that updates the points feature. Note that I think it's generally not a great idea to model a Point as a class. The overhead for an EObject seems excessive for two double values. And likely people programming against such an API will find it annoying to create a Coordinate set the two values, and they'll find it confusing that a Coordinate has a container and will be removed from one container when added to another...
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03902 seconds