Bug 443917 - When using the "Sirius" language variant in the Interpreter view, invalid Acceleo expressions fill the error log with exceptions
Summary: When using the "Sirius" language variant in the Interpreter view, invalid Acc...
Status: RESOLVED WONTFIX
Alias: None
Product: Sirius
Classification: Modeling
Component: Core (show other bugs)
Version: 1.0.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2014-09-12 05:07 EDT by Pierre-Charles David CLA
Modified: 2021-03-21 11:02 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre-Charles David CLA 2014-09-12 05:07:38 EDT
Steps to reproduce:
1. Open the "Interpreter" view and the "Error log" view (keep both visible).
2. Create and open a modeling project, with at least one semantic element, and select it in the model explorer.
3. In the "Interpreter" view, select "Acceleo" as a language variant, and make sure the "Enable real-time evaluation" switch is enabled.
4. In the "Interpreter" view, enter the expression "[self/]". The result should show up as the semantic element you selected in step 2.
5. Change the expression into "[self.e/]". Assuming your EObject does not have a feature named "e", you should see an error marker in the "Interpreter" view, no result, and no new entries in the error log.
6. Switch the interpreter into "Sirius Interpreter" mode and repeate steps 4 and 5. As soon as the expression is detected as a potential Acceleo expression (i.e it is bracketed by [.../]), every intermediate expression which happens while you edit but is invalid throws a new exception which appears in the error log.
Comment 1 Pierre-Charles David CLA 2021-03-21 11:02:32 EDT
This still happens when using the MTL syntax, but that is more or less deprecated. The bug does not occur with AQL which is the recommended language to use now.