Re: Re: PHP Frameworks - Opinion

On Wed, 2006-08-02 at 18:08 +0200, Jochem Maas wrote: > Robert Cummings wrote: > > On Wed, 2006-08-02 at 15:51 +0300, karthikeyan balasubramanian wrote: > >> Speaking about framework. Anybody is aware there is a very popular > >> framework in Java called Spring which has pretty cool features like > >> "Inversion of Control", "Dependency Injection" etc. > > > > Sounds similar to the service system implemented in InterJinn. I > > implemented a lookup system allowing retrieval of service objects by > > custom names. This allows the mapping to be overriden with userland > > re-definitions which may or may not extend the original class. In this > > way, a developer can replace components and services without the need to > > change the code that makes use of such objects. The only caveat is that > > the override must at least support the methods and properties for the > > service or component being overriden. > > I guess you'll be needing the strict method signature 'goodness'* to make > you code better and more robust heh ;-) > > (and yes I have been following *that* thread on internals) *lol* No, I don't believe in forcing the issue. For instance providing method support does not necessarily mean same signature. For instance a subclass may provide a default value in the parameters effectively changing the signature of the parent class yet still keeping compatibility. I think the "strict" thing being discussed on the internals is nice to have, but I prefer the ability to change the signature when you know what you are doing, or ultimately some kind of method overloading based on parameter types signatures :) I am in the "give PHP users the power they want" camp, and not in the "put a cage around OOP users" camp. :) Cheers, Rob. -- .------------------------------------------------------------. | InterJinn Application Framework - http://www.interjinn.com | :------------------------------------------------------------: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `------------------------------------------------------------'