Hi
On 14/10/2015 19:16, Adolfo
Sánchez-Barbudo Herrera wrote:
Hi Ed,
A couple of additional comments below:
Results are the instances/values on exit. What's the problem?
Yes, so it could be traced again on output, but since it is
necessarily a Class Instance it will be the same as the source
reference. (Unless an heroic implementation clones instances, but
that's its prpblem.)
Ah!. Yes invresolve should be Class not Table; even though it is an
implied metamodel.
{dInout,eOut,fOut,gOut,hOut}
{dInout,eOut,fOut,gOut,hOut}
{dInout,eOut,fOut,gOut,hOut}
{aIn,bIn,cIn,dInOut}
{aIn,bIn,cIn,dInOut}
{aIn,bIn,cIn,dInOut}
{aIn,bIn,cIn,dInOut}
It's all in the OCL-like equivalent. Needs a real rather than
artificial example, but that takes time.
NB. This is what I have specified. I would be pleasantly surprised
if that's exactly what Eclipse QVTo does, but hopefully it's not a
breaking evolution. I've shone a light into a number of dark
corners.
_______________________________________________
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
No virus
found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.6140 / Virus Database: 4447/10818 - Release
Date: 10/14/15
|