| Summary: | Typing iterator should not be mandatory in for Loops | ||
|---|---|---|---|
| Product: | [Modeling] Acceleo | Reporter: | Cedric Gava <gava.c> |
| Component: | Core | Assignee: | Project Inbox <acceleo-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | laurent.goubet |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
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. |
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