Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [emft-dev] [EMFatic] Alignment with OCLinEcore


I'm very happy to see that there is an advanced kind of tool support for OCL based on Xtext to come. In the context of AUTOSAR and Artop ( we are going to need such and therefore will use it (during second half of 2010 or so). In return, I can offer you to provide feedback which will result from our application of OCL and the associated tooling.

Here is a first question right away: In AUTOSAR it is important to know and take into account if a value has been explicitly set or has been left at it's default value, i.e., never been touched by the application or user. The latter case is called "uninitialized values". In EMF, this use case is greatly supported through unsettable features and the resulting the isSet()/unset() methods in the generated code. But I'm wondering if the initialization state of such feature's values can be queried at OCL level too. Are there corresponding language constructs available? If no, would it possible to add such?

Btw, I'm not sure but we maybe should shift this discussion to the newgroup/forum.



2010/3/27 Sven Efftinge <sven@xxxxxxxxxxx>
Hi Ed,

cool that you're implementing OCL in Xtext. We have similar plans for EMFatic.
We're working on a base language for Xtext (called Xbase) which allows people to create new languages which extends and reused
parts (or everything) of it. We want to implement an EMFatic editor based on it.


On Mar 27, 2010, at 8:46 AM, Ed Willink wrote:


Failure to obtain permission to bundle IMP Runtime for use by the MDT/OCL Examples editors forces a change of a approach. Fortunately Xtext provides a very attractive solution.

Support for the new EMF validation/setting/invocation delegates with OCL implementations requires an editor for Ecore files with embedded OCL expressions. MDT/OCL will therefore be developing (targetted at M7) an Xtext EssentialOCL.xtext that can be reused to support OCL document editing by a CompleteOCL.xtext and embedded OCLinEcore editing by OCLinEcore.xtext. EssentialOCL.xtext should also be re-useable by QVTr.xtext and QVTc.xtext.

Xtext would appear to make supporting simple structural languages such as EMFatic trivial.

It would appear that EMFatic and OCLinEcore will be so similar that it would be good to try to make them identical from a user's perspective and perhaps share any relevant customisations/quick fixes/validations/code templates.


     Ed Willink
emft-dev mailing list

emft-dev mailing list

Back to the top