Programming Grails - Cdn.oreilly.com

More documents

Recommendations

Info

} def leftShift(Person child) { children
Operator Implementation method a & b a.and(b) a ^ b a.xor(b) a++ or ++a a.next() a-- or --a a.previous() a[b] a.getAt(b) a[b] = c a.putAt(b, c) a > b a.rightShift(b) switch(a) { case(b) : } b.isCase(a) ~a a.bitwiseNegate() -a a.negative() +a a.positive() Being Too Groovy There’s a natural tendency to embrace Groovy fully once it be<strong>com</strong>es apparent how much it has to offer over Java. Writing highly idiomatic Groovy code can lead to the code being hard to understand, though. I’ve written cryptic code with no <strong>com</strong>ments that I’ve looked at months later and had to relearn how it works as if someone else had written it, because it was old enough that I didn’t remember working on it, and I had sabotaged myself by writing the code in a way that made sense at the time but not when I came back to it. The phrase I use for this is “be lazy but not sloppy.” By this, I mean save yourself time (and typing) and take advantage of Groovy’s cool features—but don’t overdo it and make your code hard to work with and understand. def Considered Harmful One example of being “too groovy” is overusing the def keyword. Optional typing is very convenient, but specifying the type can help other readers of your code (and even yourself). Naming variables and methods well makes code more self-documenting, and the same goes for whether to type variables. For example, consider this relatively information-free line of code: def foo = bar(5, true) It’s not at all clear what foo is or what you can do with it. If it’s a string, call it a String (or whatever the type is). I usually don’t type both sides of an assignment, so because it’s clear that strings is a List from the right side of the assignment, I’m okay with: def Considered Harmful | 31
Page 2 and 3: Want to read more? Spreading the kn
Page 4 and 5: Table of Contents Preface. . . . .
Page 6 and 7: Data Validation 69 Custom Validatio
Page 8 and 9: Custom Configurations 148 Mapping V
Page 10 and 11: Monitoring and the Cloud Foundry UI
Page 12 and 13: standalone utility applications. Ju
Page 14 and 15: Collections and Maps Creating and p
Page 16 and 17: The default scope for classes, fiel
Page 18 and 19: Decompiling with JD-GUI I highly re
Page 20 and 21: println hello.getClass().superclass
Page 22 and 23: } }; This can be invoked from Groov
Page 24 and 25: You’ve already seen how property
Page 26 and 27: with: String s = someMethod(...) if
Page 28 and 29: or you could just skip the whole fo
Page 30 and 31: Using a StringBuilder (the preferre
Page 32 and 33: Every Groovy class implements the g
Page 34 and 35: You called add with args [2, 3] nul
Page 36 and 37: The output from the above code is:
Page 38 and 39: assert [alJones, jedSmith, zakJones
Page 42 and 43: def strings = [] but when the right
Page 44 and 45: See the Groovy 2.0 release notes an

Programming Grails - Cdn.oreilly.com

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?