Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 330794 - Typing iterator should not be mandatory in for Loops
Summary: Typing iterator should not be mandatory in for Loops
Status: CLOSED WONTFIX
Alias: None
Product: Acceleo
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-22 07:49 EST by Cedric Gava CLA
Modified: 2016-03-29 09:42 EDT (History)
1 user (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 Cedric Gava CLA 2010-11-22 07:49:00 EST 
Build Identifier: 20100917-0705

See M2T Forum, MSG 640457 in thread "[Acceleo 3] Iteration over the types of a model"
In OCL, typing Iterator is not mandatory, but If you try to do the same in Acceleo, compiler raises a syntax error. 
[for (a : String |Sequence{'a','b','c'})][/for] works
[for (a |Sequence{'a','b','c'})][/for] shall work too



Reproducible: Always

Steps to Reproduce:
1. Create a for loop : [for (a |Sequence{'a','b','c'})] [/for]
2. Compiler shall not raise a syntax error
Comment 1 Laurent Goubet CLA 2016-03-29 09:42:47 EDT 
Modifying the parser to cope with untyped variables is far from easy in the current state of things (variables don't have access/knowledge about the iteration set's typing) and will not be done until we change parsers.