Thank you. I just thought that a GEP would have been a good thing because the way this feature has to work is not completely clear for me. E.g : I didn't think about the way to pass the sender of an event to the closures or the way to constraint the closures parameter types.
Le 23 avril 2015 00:52:37 GMT-11:00, Jochen Theodorou <[email protected]> a écrit : >Am 24.04.2015 02:28, schrieb CH: >> Sorry, what is a GEP ? > >Groovy Enhancement Process (GEP) > >http://docs.codehaus.org/display/GroovyJSR/GEP+1+-+Groovy+Enhancement+Proposal > >> Do you have some documentation about the testing procedures in the >project so I have something to take as a reference for this work ? > >usually we do junit3 style tests using GroovyTestCase for stuff in >core, >like where this would be. At least for API tests. For test of the >language side we usually use assertScript(String) method from the test >case, which allows you to write a small script, including helper >classes >and all in a multiline string > >> And finally, do you have rules about the présentation of the code >like curly brackets on a new line or not, etc.? > >normally { on the same line (unless it is too long) and spaces between >operators, ident as spaces (4). Everything else usually just works out. > >If there is something too terrible looking we will tell you ;) > >bye blackdrag > >-- >Jochen "blackdrag" Theodorou >blog: http://blackdragsview.blogspot.com/
