Details
-
Type:
Sub-task
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.0-beta-1
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
coming from Java it is a bit difficult for some users to find their way into dynamic programming, especially when it comes to method being there or not. therefor I suggested an annotation with source visibility, that can be used by the compiler to check if a method actually exists. This will slow down compilation a bit and may not be supported by IDEs as of yet. Also the check will be a check only, it will not force any kind of method selection at runtime. I suggested to let the compiler throw an error if the annotation forces compiler to check if a method exists, but is unknown, because I am against warnings. the annotation should be used at method or class scope.
Activity
We are about to start a project under the name Grumpy, which will do static checking of Groovy code. Don't be afraid, it is only the name till we find a better one 
With this only a subset of Groovy will compile. But it will check method calls and assignments like in Java. Would this help you in your case?
Sounds good Jochen. I will keep a look out for further details.
But sorry, I can't give you a +1 on the name 
My company haS a rather large framework built on java and groovy. We prefer to code in groovy than java, but we miss compile-time checks when we are not using dynamic language features such as method missing. When your code base grows over 200k LOC, then compile time interface checking is a nice option.
It would be nice to be able to instruct the compiler to throw errors when compiling modules/classes/methods that we explicitly tell it don't use dynamic stuff.