[GROOVY-2555] Calling abstract super method causes stack overflow instead of compiler error

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.5.2, 1.6-rc-2
• Fix Version/s: 1.5.6, 1.6-beta-1
• Assignee: Paul King
• Reporter: Mike Dillon
• Created: 30/Jan/08 02:15
• Updated: 27/Apr/08 04:51
• Resolved: 15/Apr/08 20:07

Description

I accidentally wrote some code that called an abstract method on a superclass and received a StackOverflowError instead of a compiler error (the method was calling itself despite the "super."...). Doing the same thing in Java results in an error like "abstract method theMethod() in A cannot be accessed directly" and I think Groovy should probably do something similar (see the attached test case).