![Groovy Programing Language ,[object Object]](https://image.slidesharecdn.com/exoec-groovyprogramminglanguage-090820113359-phpapp02/85/eXo-EC-Groovy-Programming-Language-1-320.jpg)
![Apply better practice to our groovy templates ,[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (20)
Similar to eXo EC - Groovy Programming Language
Similar to eXo EC - Groovy Programming Language (20)
More from Hoat Le
More from Hoat Le (14)
Recently uploaded
Recently uploaded (20)
eXo EC - Groovy Programming Language
- 3. Develop Grails with Flex and deploy on Google App Engine or Spring Source Cloud
- 5. Let's play with Groovy
- 6. Some basic differences from Java
- 8. Anything in Java but not in Groovy
- 10. Best practices
- 12. Now Java bloats with too many frameworks, libs... -> many organizations have to consider Ruby, LAMP, .NET for more productive and agile at lower costs
- 13. Groovy appeared in 2003 – promising more complete and dynamic language for JVM instead of Ruby, Python, or JavaScript implementation for JVM.
- 15. Switch “Hello World” Java to Groovy
- 17. java.math
- 18. java.net
- 19. java.util
- 20. groovy.lang
- 21. groovy.util
- 23. Java: if (mySet == null || mySet.isEmpty()) {
- 24. ...
- 25. }
- 26. Groovy:
- 27. if (!mySet) {
- 28. ...
- 29. }
- 31. ?: (ELVIS!)
- 32. *. (THE SPREAD-DOT OPERATOR)
- 33. <=> (COMPARISONS WITH A SPACESHIP)
- 34. ${} (GROOVY STRINGS)
- 35. [] (ARRAY-STYLE NOTATION FOR LISTS AND MAPS)
- 37. No “DO...WHILE”
- 38. Inner and anonymous classes: Not fully supported
- 40. [ "apple", "pear", "cherry" ].each { println it }
- 41. Duck Typing : Applied to dynamic languages, it means that if an object has a particular property or method signature, then it doesn’t matter what type the object is, you can still call that method or access that property. This is only possible in dynamic languages because properties and methods are resolved at runtime.
- 43. Experiment
- 44. Use methods where appropriate
- 45. Use explicit types in method signatures