Re: [RFC] E_NOTICE for invalid array container

Dan, You're right on both accounts; also, as I just notices it could easily have other BC-breaks (although expecting errors in a certain format is odd) through calls like error_get_last(), which would regardless of INI settings include this NOTICE. I will update the RFC with these changes. -- Dave On Mon, Aug 1, 2016 at 4:27 PM Dan Ackroyd <danack@basereality.com> wrote: > Hi David, > > The updated section still doesn't really describe the BC break that well. > > Some people will need to change their code to avoid having notices > raised frequently. How difficult that will be needs to be thought > about. > > Additionally, although the default ini files may turn off notices in > production environment, I really don't believe that is best practice. > For my machines, in both production and dev all warnings and notices > (except deprecation notices in production) are converted into > exceptions. Anything else allows mistakes in code to go undetected. > > cheers > Dan >