--- George Schlossnagle <[EMAIL PROTECTED]> wrote: > On Jun 16, 2005, at 2:50 PM, boots wrote: > > --- Andi Gutmans <[EMAIL PROTECTED]> wrote: > > > >> You missed the point of E_STRICT. I introduced it as an > E_PEDANTIC. > >> That was the whole idea. To be pedantic about code that works, > not > >> to warn about code that doesn't work (which is for higher warning > >> levels) > >> > > > > I don't think I missed that, I just don't appreciate it :) > > If you don't want pedantic checks, don't run with E_STRICT.
As a developer, I want to run with E_STRICT, or at least, I want to know what the engine thinks in regards to the correctness of my code. That is not the problem. The problem is that I can't control what customer environments and I don't necessarily want to port perfectly acceptable PHP4 code to avoid warning on their systems. The point is that E_STRICT is meant for developers but is implemented in the general runtime where it impacts more than just developers. Well, you were all kind enough to allow me to have my say so I will leave it in your capable hands now and accept your decisions. Thank-you. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
