Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313773 - Syntax of iterate operation (EOL)
Summary: Syntax of iterate operation (EOL)
Status: CLOSED INVALID
Alias: None
Product: Epsilon
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Dimitris Kolovos CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-20 13:03 EDT by Chris Holmes CLA
Modified: 2012-06-26 16:10 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 Chris Holmes CLA 2010-05-20 13:03:04 EDT 
The syntax of the iterate operation as described in the Epsilon Book, e.g. 
var msbs   : OrderedSet(Integer) := self.getFields().collect(field | field.msb).asOrderedSet();
var maxMsb : Integer             := 0;
msb := msbs.iterate(msb : Integer;  x : Integer = 0 | msb.max(x));

The iterate operation fails to parse, although I think this conforms to the format identified in the Epsilon book. This form also fails to parse:
msb := msbs.iterate(msb;  x=0 | msb.max(x));

Discussed with Dimitris 20-May-2010
Comment 1 Ralph Gerbig CLA 2011-08-23 07:48:23 EDT 
(In reply to comment #0)
> The syntax of the iterate operation as described in the Epsilon Book, e.g. 
> var msbs   : OrderedSet(Integer) := self.getFields().collect(field |
> field.msb).asOrderedSet();
> var maxMsb : Integer             := 0;
> msb := msbs.iterate(msb : Integer;  x : Integer = 0 | msb.max(x));
> 
> The iterate operation fails to parse, although I think this conforms to the
> format identified in the Epsilon book. This form also fails to parse:
> msb := msbs.iterate(msb;  x=0 | msb.max(x));
> 
> Discussed with Dimitris 20-May-2010

Is there anything new on this Bug?
Comment 2 Dimitris Kolovos CLA 2012-06-26 16:10:23 EDT 
iterate() is no longer supported in EOL so I suspect it makes sense to close this bug as invalid