Re: Compatibility problems with PHP 5

At 02:37 PM 12/1/2003 -0500, Daniel Convissor wrote:

On Sun, Nov 30, 2003 at 01:10:25AM +0200, Andi Gutmans wrote: The strict was introduced so that we can add warnings about practices we recommend and deprecated behavior. I think "var" belongs there. We could remove E_STRICT from E_ALL (although that'd be a bit hacky) and save ppl the trouble of seeing these warnings. Again, turning off E_STRICT stops people from seeing major deprication issues. Declaring a class variable via "var" vs "public" is not a major deprication problem at this point in time. E_STRICT is creating a major problem. Pepole who provide classes for public consumption -- and there are a lot of us out here -- would be forced to maintain/distribute two branches of code: one using var for PHP 4 users, one using strict for PHP 5 users. All I can say is "PLEASE don't make this scenario come true."

I don't quite understand the problem. E_STRICT was only meant for people who really want to be pedantic. I think we can make it not part of E_ALL. Is that OK? Andi