Re: [qvto-dev] Hiding of module properties

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi

UML has private/protected/public visibility, which OCL (and QVT) ignores. So I think all properly qualified unambiguous names should be useable in QVTo.

    Regards

        Ed Willink

On 09/05/2014 15:03, Christopher Gerking wrote:

Hi everybody

 

Should QVTo support hiding of properties between modules? On the one hand, there is a test case called “importedVirtuals”, which seems to rely on this practice. On the other hand, there is an error message ValidationMessages.ModulePropertyAlreadyDefined, which clearly states that a property from an imported module may not be defined again (the QvtOperationalVisitorCS code doesn’t enforce this, though). What’s your opinion?

 

 

Regards

Christopher

 

 

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

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4577 / Virus Database: 3931/7462 - Release Date: 05/08/14