[qvto-dev] QVT 1.3 Typedef issues

[Ed Willink <ed@xxxxxxxxxxxxx>]

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