Each signature should hold in some way the following info (at least): · Ruby method. · Java method. · Parameters for the Java method. · Return value. · Visibility and such. · Annotations
I suggest discussing the first four, choose two or three ideas, implement them in different branches and start playing a bit with them. Starting points: · If you can call the ruby method with n parameters, then you can make a Java method with n parameters (note that the implication is one way only). · One should be able to generate a signature knowing only the ruby method name, the type of the params and the retval. Preferences: · Java method name is the same as ruby method, unless stated otherwise (by the same, I mean that find_by_name would be findByName). · An option to generate multiple signatures for one ruby method should be given. This lead me to what I said. Anyway, I think that currently the code is small enough to make two or three branches with the main ideas and play a bit (I don't know if I've said already this). Cheers, Serabe -- http://www.serabe.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
