On Tue, Jan 26, 2010 at 9:39 PM, Esko Luontola <[email protected]>wrote:
> On Jan 26, 2:28 am, Clinton Begin <[email protected]> wrote: > > Let your community speak for itself, as I'm sure it will. ;-) > > Makes sense. > > Would you still please say on this mailing list, that what were the > design decisions that lead to the requirement of @Inject? There are > quite many frameworks which have gone the other way, that they inject > constructors without any annotations. What are the pros and cons of > either approach? > > It is simply not true that we mandate the requirement of @Inject. We simple encourage it as a good practice for readability and self-documentation. Guice is perfectly capable of injecting any constructor in your classes. Perhaps Bob Martin has missed this point too? Dhanji. -- 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.
