-
Key: QVT13-22
-
Legacy Issue Number: 18323
-
Status: closed
-
Source: campus.upb.de ( Christopher Gerking)
-
Summary:
The spec should clarify the interaction of
1.) explicit instantiation + execution of 'accessed' transformations, and
2.) trace records / resolving.The following questions are of interest:
How does the initial trace for an 'accessed' transformation look like? Does it reuse the records previously created by the 'accessing' transformation, or does an 'accessed' transformation always start on an empty trace?
How does an 'accessed' transformation affect the trace? Are the trace records post-visible that were created during execution of the 'accessed' transformation, or is the trace of the 'accessing' transformation unchanged?
Both issues heavily affect the results of resolve-operations. Resolving object references after executing an 'accessed' transformation would be very practical.
-
Reported: QVT 1.1 — Thu, 27 Dec 2012 05:00 GMT
-
Disposition: Duplicate or Merged — QVT 1.3
-
Disposition Summary:
Trace data for an 'accessed' transformation
The spec should clarify the interaction of
1.) explicit instantiation + execution of 'accessed' transformations, and
2.) trace records / resolving.The following questions are of interest:
How does the initial trace for an 'accessed' transformation look like? Does it reuse the records previously created by the 'accessing' transformation, or does an 'accessed' transformation always start on an empty trace?
How does an 'accessed' transformation affect the trace? Are the trace records post-visible that were created during execution of the 'accessed' transformation, or is the trace of the 'accessing' transformation unchanged?
Both issues heavily affect the results of resolve-operations. Resolving object references after executing an 'accessed' transformation would be very practical.
Discussion
The resolution of
QVT13-23makes clear that the trace data contains a trace record for every mapping. -
Updated: Tue, 29 Mar 2016 15:09 GMT