Hi Nikita, > If named parameters are introduced, signature validation should include > parameter names. Throwing a fatal error (for the interface/class combination) > would break backwards compatibility though. We could use some lower error > type...
Would it be possible to set the error level through an ini setting? Or disable it entirely? People who are writing new code that is aware of named parameters should want a fatal error for any coding mistake that violates the contract. People who are supporting legacy code that doesn't use named parameters should be able to upgrade to the latest version of PHP without having to refactor an entire code base or suppressing huge numbers of compiler warnings. cheers Dan On Fri, Sep 6, 2013 at 5:39 PM, Nikita Popov <nikita....@gmail.com> wrote: > Hi internals! > > I created an RFC and preliminary implementation for named parameters: > > https://wiki.php.net/rfc/named_params > > The RFC and implementation are not yet complete. I mainly want to have > feedback on the idea in general and on the Open Questions ( > https://wiki.php.net/rfc/named_params#open_questions) in particular. > > Thanks, > Nikita >
