QVT13 — QVTc/QVTr: Pattern.bindsTo composition

The author of Issue 9379 misunderstood the poor description of Pattern::bindsTo and consequently removed the

.

There was actually nothing wrong with bindsTo that could not have been fixed by clearer wording to the effect that bindsTo was a dustbin container for variables not contained elsewhere.

The above kind of emphasises the benefits of an ownedPlurals naming policy. Therefore suggest that:

a) the AST bloat from the redundant bindsTo be replaced by definition of a suitable derived property that satisfies the intent of all variables.

b) that variables be renamed ownedVariables and used throughout the QVTr to QVTc transformation

Rewind Issues 9379, 10938

The author of Issue 9379 misunderstood the poor description of Pattern::bindsTo and consequently removed the

.

There was actually nothing wrong with bindsTo that could not have been fixed by clearer wording to the effect that bindsTo was a dustbin container for variables not contained elsewhere.

The above kind of emphasises the benefits of an ownedPlurals naming policy. Therefore suggest that:

a) the AST bloat from the redundant bindsTo be replaced by definition of a suitable derived property that satisfies the intent of all variables.

b) that variables be renamed ownedVariables and used throughout the QVTr to QVTc transformation

Discussion

The problem is genuine, but further Eclipse QVTr prototyping reveals two distinct cases, one requiring containment, another not. Further work is needed to specify these accurately.