Bug 525257 - Make interpreted expressions variables handling more complete and reliable
Summary: Make interpreted expressions variables handling more complete and reliable
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Core (show other bugs)
Version: 4.1.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: Next   Edit
Assignee: Project inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on: 424208 447715 447725 455067 457459 465956 470598 470722 481481 487316 491383 494732 508252 513309 516879 476523
Blocks:
  Show dependency tree
 
Reported: 2017-09-27 03:40 EDT by Pierre-Charles David CLA
Modified: 2018-08-21 09:58 EDT (History)
2 users (show)

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 Pierre-Charles David CLA 2017-09-27 03:40:44 EDT 
This is a "meta-issue" to make it easier to track all the concrete issues already reported concerning these issues:
* variables missing completely when they would be useful for specifiers;
* inconsistencies between completion (in the VSM editor), validation (in the VSM editor), documentation (in the tooltips and in the manual), and actual behavior at runtime;
* type inference not precise enough (which leads to more complex expressions full of "oclAsType" or false positives in validation).
Comment 1 Pierre-Charles David CLA 2017-09-27 05:06:59 EDT 
Note that there are two possible approaches here, not sure which one we'll take:
* fix all the individual issues we know about while keeping the existing code/infrastructure.
* overhaul the whole mechanism with a solution that ensures completeness and consistency by construction (something akin to what is described in bug #496078).