[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [qvto-dev] QVT 1.3 Typedef issues
|
Hi
I'm not yet familiar with typedefs. Could you provide examples for 2) and 3) ?
-----Ursprüngliche Nachricht-----
Von: qvto-dev-bounces@xxxxxxxxxxx [mailto:qvto-dev-bounces@xxxxxxxxxxx] Im Auftrag von Ed Willink
Gesendet: Montag, 5. Oktober 2015 22:35
An: QVTOML developer mailing list <qvto-dev@xxxxxxxxxxx>
Betreff: [qvto-dev] QVT 1.3 Typedef issues
Hi
Adolfo raised a couple of issues that question the integrity of typedef in QVTo.
1) The Constrained Typedef seems to be an underspecified QVTo-specific syntax bloat that could be handled in a general UML-specified way by a Class with an invariant.
2) The added operations library type typedef seems to be an irrelevant SmartQVT implementation detail that conflicts with Complete OCL.
3) Only the textual type synonym has integrity and utility.
Is it going to cause a problem if 2) is deleted completely, 1) is strongly deprecated with the Typedef AS class shrinking to an Element subclass that persists the textual macro for 3).
Regards
Ed Willink
_______________________________________________
qvto-dev mailing list
qvto-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/qvto-dev
