Re: Compatibility problems with PHP 5

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." --Dan -- FREE scripts that make web and database programming easier http://www.analysisandsolutions.com/software/ T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y 4015 7th Ave #4AJ, Brooklyn NY v: 718-854-0335 f: 718-854-0409