Ed,
Sorry for the delayed response.
I see
three options:
a) Do nothing. Xtext is only an example. It is not fully integrated.
b) Add parsing that ignores an import statement to the LPG parser. A
bit close to M7, but it only affects the CompleteOCL grammar. Users
still need to configure the LPG environment.
c) Fully support an import statement in the LPG parser. As above, but
we also need to load the registry, eliminating the need for users to
configure registries externally.
I favour b), creeping to c) if time allows, with an intent to have c)
in 3.0.1.
I haven't investigated anything about your xtext editors, so I can't
yet imagine how you are mixing Xtext editors with the current OCL API.
Due to the we are so close to M7, I would have said a). However, due to
the fact that you have made great improvements with the xtext editor, I
hope you have a better idea if you are in time to obtain b). I wouldn't
do c), we would need some discussions about the "import statement",
probably and firstly at OMG RTF.
----------------
Elimination of the IMP editors renders the
org.eclipse.ocl.examples.parser.* plugins redundant, which in turn
leaves the org.eclipse.ocl.examples.modelregistry.* plugins redundant,
and if OCL (and QVTd) has an import statement there is limited
motivation to reintroduce it.
QVTd has not yet migrated to exploit the OCL Model Registry and I would
be amazed if anyone else has. QVTo is not affected.
I favour dropping the org.eclipse.ocl.examples.editor.*,
org.eclipse.ocl.examples.parser.* and
org.eclipse.ocl.examples.modelregistry.* plugins.
I think that the model registry has been a feature of interest, not
only for QVTd editors. I think it's quite independent from other
example plugins, isn't it ?. If dependencies are not a problem, I don't
see any problem about providing the model registry as an example.
Cheers,
Adolfo.
Regards
Ed Willink
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
|
