Hi Bulat,

thanks for this .. really cleans things up nicely.
generally i prefer constructor injection, because it makes it easy to spot all 
the dependencies by just looking at the constructor. furthermore it reduces the 
risk of getting an instance that isnt fully initialized yet.

i guess for interface injection it cannot really be combined with constructor 
injection though, then again since it also puts the dependencies in a central 
location its not so much an issue that the interfaces then use setters.

cool stuff.

regards,
Lukas Kahwe Smith
[email protected]



-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony developers" 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/symfony-devs?hl=en

Reply via email to