Parameter directions shall be enforced

[eclipse-viatra-bot]

| --- | --- | | Bugzilla Link | 501465 | | Status | NEW | | Importance | P3 normal | | Reported | Sep 15, 2016 03:21 EDT | | Modified | Nov 23, 2020 08:30 EDT | | Version | 1.4.0 | | Depends on | 530515 | | Reporter | Balazs Grill |

Description

Since 1.4.0 M2, it is possible to set directions to pattern parameters. To enforce these constraints on the usage of the patterns, the following changes shall be implemented:

• remove invalid API from generated matches
  • OUT parameters shall not be represented on constructors
  • setters shall be generated only for IN and INOUT parameters
  • getters shall be generated only for OUT and INOUT parameters
• language validators for pattern calls
  • Cannot call an in parameter with '_'

[eclipse-viatra-bot]

By Abel Hegedus on Sep 15, 2016 04:12

I disagree with these suggestions:

• The user should be able to create a mutable match with any substitutions, since these DTOs are used outside of matcher code (e.g. EVM filters or query results view).
• I thought you wanted to remove type-safe generated matcher methods, though this is not listed here.
• Finally, the internal backend code should check that the actual call is correct for the given pattern and possibly throw an unchecked exception if it cannot deal with it.

The language validator part seems OK.

[eclipse-viatra-bot]

By Zoltan Ujhelyi on Jan 25, 2017 08:07

Postponed.

[eclipse-viatra-bot]

By Zoltan Ujhelyi on Oct 04, 2017 05:04

Postponing.

[eclipse-viatra-bot]

By Zoltan Ujhelyi on Nov 20, 2019 05:51

Postponing issues to the next release.

[eclipse-viatra-bot]

By Zoltan Ujhelyi on May 18, 2020 13:04

Postponing issues that will not be solved for version 2.5.

[eclipse-viatra-bot]

By Zoltan Ujhelyi on Nov 23, 2020 08:30

Mass postponing of issues to the 2.6 timeframe.