Re:Google Java Annotations Gallery
by kinofcain on Monday May 27, 2013 @05:11PM
(#5776608)
I think it's valid since Life, in this case, extends Box of Chocolates and therefore "is a" Box of Chocolates. If Life had implemented the same interfaces or extended the same parent class as Box of Chocolates, then it would be a @simile as Life, in that case, would be "like a" Box of Chocolates.
Re:Google Java Annotations Gallery
by galaktor on Monday May 27, 2013 @08:49AM
(#5774457)
Looks fun. I assume it's still up to the application devs as to how they handle those annotations then (say on a build server or when the docs are generated)? Unless I'm missing something, there doesn't appear to be any direct effect of using them other than the meta-data that they add.
Edit: looks like "gag-agent" is there to react to the annotations, but it's not clear to me where/how that would work
Re:Google Java Annotations Gallery
by tokenizerrr on Monday May 27, 2013 @09:18AM
(#5774537)
It's mostly there to send messages to your fellow programmers, it seems. The instrumentation jar will enforce the behaviors of the annotations under the Enforceable category.
Re:Google Java Annotations Gallery
by tekacs on Monday May 27, 2013 @10:34AM
(#5774753)
Strangely compelling, even.
Something that almost seems as though it wouldn't be completely out of place in a production codebase (though you'd probably want to ensure that they were elided or at least renamed before shipping :P).
Is it talking about that PG?
"SIMILE: a figure of speech comparing two unlike things that is often introduced by like or as (as in cheeks like roses).
“She's as fierce as a tiger” is a simile, but “She's a tiger when she's angry” is a metaphor."
Edit: looks like "gag-agent" is there to react to the annotations, but it's not clear to me where/how that would work
Something that almost seems as though it wouldn't be completely out of place in a production codebase (though you'd probably want to ensure that they were elided or at least renamed before shipping :P).