[GROOVY-3284] Call behavior on enums is inconsistent

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.5.7
• Fix Version/s: 1.6.1, 1.5.8, 1.7-beta-1
• Environment: XP, cygwin, JRE 1.6.0
• Assignee: Roshan Dawrani
• Reporter: Chris Currivan
• Created: 15/Jan/09 10:44
• Updated: 07/Apr/09 23:31
• Resolved: 06/Feb/09 13:22

Description

A call method on an enum can be used within a for loop, but not otherwise. This is kind of odd, and it might be better to disable the for loop behavior if it's not reasonable to fix in general.

 

enum Foo {
    A({ println("A") }),
    B({ println("B") })
    Foo(Closure c) {
      call = c
    }
    final Closure call
}

// works
for (f in Foo) {
   f()
}

// works
Foo.A.call()

// doesn't work
Foo.A()

// doesn't work
a=Foo.A
a()