I don't feel strongly about @Inject one way or another but the more
I hear in favor of explicit @Inject the less sense it makes to me.
1) Why would you want to identify these classes in the first place? I
mean, who cares whether the class is created by Guice or by someone else?
2) Is this ability worth the cost of explicit annotations? Is it worth
losing the ability to inject/integrate with 3rd-party libraries?
3) Doesn't @Inject just mean that it *can* be injected by Guice, not
that it necessarily is? Don't user Modules already give you most of this
information anyway?
Sorry to beat a dead horse :) I'm also surprised that no one else in
the community has an opinion (either way) on this matter...?
Gili
Bob Lee wrote:
> Ah, but when you're looking for callers in a non-Guice-aware IDE (or
> just plain reading the code), the @Inject makes it obvious that this
> class is injected by Guice. That wouldn't be immediately obvious
> otherwise.
>
> FWIW, I'm pretty sure Josh would agree with me here.
>
> Bob
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"google-guice" 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/google-guice?hl=en
-~----------~----~----~----~------~----~------~--~---
