Re: RfC: rethink OO inheritance strictness

Hello, On Thu, 03 Aug 2006 10:48:38 +0300 zeev@zend.com (Zeev Suraski) wrote: > Actually no, what Derick said is what I meant. > > I think emitting an E_STRICT notice on violation of a signature is a > very reasonable compromise between the loose and strict worlds. It's > not scientifically proven, but I very much believe that there's very > strong mapping between those who care about these signatures and > those who have E_STRICT enabled. Yes and no. Yes because E_STRICT already contains some OO only warnings and no because there is many problems catched by E_STRICT that are not related to OO good/bad practices, but they are still important and should be fixed. That's again the same problem, like many other I do develop with the most verbose method to prevent any kind of technical troubles (now or later) with my applications. I do not consider this issue as a technical problem. But having such annoying E_STRICT warnings prevent me to use it. > I don't see why we need to add any new modifiers, loose or strict. I don't see why PHP has suddenly to enforce design rules either, but you know that. -- Pierre