Hi
Because the context can only be a Class instance, I think my words
are ok.
What is traced surprised me when I pinned it down. But to trace the
non-parameters would require deep tracing of object construction
helpers. It's just not practical. You could have a 'traceable' tool
option that prohibited all use of object construction that was not
observable through mapping tracing, and which prohibited untraceable
object mutation and ....
My words are my best attempt to expose what is already suggested. In
part they are a provocation to Christopher or Sergey to object to
them. This all started with from Christopher's query about what does
get traced. Christopher clearly doesn't object to them. Sergey
hasn't commented.
Unless someone identifies a real problem causing me to withdraw the
resolution, that's probably what will materialize.
Regards
Ed Willink
On 14/10/2015 21:51, Adolfo
Sánchez-Barbudo Herrera wrote:
_______________________________________________
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/10820 - Release
Date: 10/14/15
|