Substituting Java for Groovy Little By Little
Posted
by yar
on Stack Overflow
See other posts from Stack Overflow
or by yar
Published on 2010-02-12T16:10:51Z
Indexed on
2010/06/02
21:24 UTC
Read the original article
Hit count: 398
I have been checking out Groovy a bit and I feel that moving a Java program to Groovy little by little -- grabbing a class and making it a Groovy class, then converting the method guts a bit at a time -- might be a relatively sane way to take advantage of some of the Groovy language features. I would also do new classes in Groovy.
Questions:
- Is this a reasonable way to convert?
- Can I keep all of my public methods and and fields in Java? Groovy is "just" a superset, right?
- What kinds of things would you not do in Groovy, but prefer Java instead?
© Stack Overflow or respective owner