> I for one welcome our new E_STRICT overlords. Now that I've stopped laughing, let me say that I agree. I think all of us agree. As Wombert asked, what is the code that it's actually choking on?? ;) --Bob
On 9/8/05, Daniel Swarbrick <[EMAIL PROTECTED]> wrote: > Cyril Ucron David wrote: > > that's a backward incompatible change made in PHP the only easy way > > out is not to use strict use E_ALL & ~ E_NOTICE & ~ E_STRICT > > > > On 9/8/05, Greg Donald <[EMAIL PROTECTED]> wrote: > > > >>I upgraded my PHP to 5.0.5 yesterday. After that my Agavi project > >>began throwing warnings: > >> > > It would be nice to get Agavi E_STRICT-compliant - PHP has been too > leniant on sloppy code in the past, and I for one welcome our new > E_STRICT overlords. E_STRICT code should ultimately be more portable in > future. > _______________________________________________ > agavi-dev mailing list > [email protected] > http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev > _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
