[GROOVY-254] range precedence should be fixed

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Fix Version/s: 1.0
• Component/s: parser
• Assignee: Unassigned
• Reporter: James Strachan
• Created: 10/Mar/04 05:55
• Updated: 05/Dec/04 04:05
• Resolved: 22/Mar/04 07:54

Description

we should probably allow

1..3.each

{...}

or

1..3.toList()

and so forth to mean

(1..3).methodCall

right now the method applies to the '3' rather than the range