Don't get me started on Annotations.. what annoys me about them, is
that while they are soft data implemented as first class classes.
Meaning, to inspect a runtime annotation, the annotation must be in
the classpath. You might forgive that (claiming its a dependancy)
Yet the annotation simply contains Strings and/or primitives in some
kind of template Seems to be the worst of both worlds - No real types
in that you are forced to reference say, class names as Strings, but
the annotation itself is a real type which must resolve. I don't
claim to be an expert on annotations, havent used them that much, but
perhaps they would have been nicer if they were value holders but
simply permitting no code...
@ReturnClass( Blah.class )
public Class getSpecialClassThingy(Obect thing) {
This is just off the top of my head. Forgive all errors of logic. :)
You could return Class<Blah> but that's not reflectable anyway.. but
that another thread.. :)
On Sep 5, 8:15 am, Casper Bang <[EMAIL PROTECTED]> wrote:
> We used to say "If it compiles, the crap works". Now a day, with all
> the annotation cr... stuff, this doesn't seem to hold true any longer.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "The
Java Posse" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en
-~----------~----~----~----~------~----~------~--~---
