Bug 511026 - [qvts] Bad code for re-navigated optional paths
Summary: [qvts] Bad code for re-navigated optional paths
Status: NEW
Alias: None
Product: QVTd
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-25 07:27 EST by Ed Willink CLA
Modified: 2017-03-06 14:03 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2017-01-25 07:27:43 EST 
If (Bug 509404) the catch of null navigation errors is removed, testQVTcCompiler_Forward2Reverse_CG fails with a bad navigation from forwardList.headElement which was not in the original QVTc.

Unfortunately the *.qvtcas cannot be viewwed to see if it shows a null navigation hazard, since there is some kind of editor load failure on a model leading to too many proxies.
Comment 1 Ed Willink CLA 2017-03-06 14:03:14 EST 
(In reply to Ed Willink from comment #0)
> Unfortunately the *.qvtcas cannot be viewwed to see if it shows a null
> navigation hazard, since there is some kind of editor load failure on a
> model leading to too many proxies.

Bug 513194

> If (Bug 509404) the catch of null navigation errors is removed,
> testQVTcCompiler_Forward2Reverse_CG fails with a bad navigation from
> forwardList.headElement which was not in the original QVTc.

The QVTs diagram shows that forwardList.headElement is the first of a three element chain of optional elements.

QVTs2QVTi should synthesizing these using safe navigations since null is a valid value. 

The test currently passes since the required null assignment is the default and so the premature exit via an erroneous null source guard doesn't matter so long as the erroneous exit is also (erroneously) ignored.