RE: [m2m-dev] Does qvt operational support the transformation extension

["Alexander Igdalov" <Alexander.Igdalov@xxxxxxxxxxx>]

Hi Marcel,

See answers inlined below.

> Is it correct that the mechanisms 'extend' and 'accept' don't work for
transformation reuse?

Yes and no. At the moment we do not support access-mechanism. As for
module import, QVTO inherited the legacy semantics from Borland Together
QVT. In accordance with it, the 'import' statement not only denotes the
traditional package import but also makes the importing transformation
inherit all mappings, helpers, etc. from the imported transformation. In
this way, it actually implements the 'extends'-semantics. However, such
implementation is non-standard.
As for access/extends syntax - it is supported in grammar only. Attempts
to use it cause a corresponding compiler warning.

> Do you have in focus to implement these features in the near future?

Yes. Since we are planning to become fully compliant with the QVT
specification, we are permanently reducing deviations between our
implementation and the QVT standard. Transformation reuse mechanism is
one of our future goals.

Cheers,
Alex.

P.S. I would kindly refer you to the M2M newsgroup at news.eclipse.org
which is the most suitable place for questions like this.

-----Original Message-----
From: m2m-dev-bounces@xxxxxxxxxxx [mailto:m2m-dev-bounces@xxxxxxxxxxx]
On Behalf Of Marcel Becker
Sent: Tuesday, February 03, 2009 10:09 PM
To: m2m-dev@xxxxxxxxxxx
Subject: [m2m-dev] Does qvt operational support the transformation
extension and access mechanisms?

Dear M2M Team!

Is it correct that the mechanisms 'extend' and 'accept' don't work for
transformation reuse?

Do you have in focus to implement these features in the near future?

Or do you know an existing implementation of QVT which supports
transformation extensions?

Thank you very much!

Marcel

_______________________________________________
m2m-dev mailing list
m2m-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2m-dev