Re: Compatibility problems with PHP 5

For the next 18-24 months, we are going to have to deal with code running in both PHP 4 and 5. Why not declare "var" an alias for "public", not throw E_STRICT for it and be done with it? If not this issue will be a real PITA for PEAR users. - Stig On Sun, 2003-11-30 at 00:10, 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. > Then again, we could remove the warning about var but I'm not sure I'd want > to do that. > > Andi > > At 12:22 PM 11/28/2003 -0500, Daniel Convissor wrote: > >On Fri, Nov 28, 2003 at 10:04:39AM +0100, Derick Rethans wrote: > > > > > > Strict is strict, that's the whole point. You can either fix your code > > > or disable strict. > > > >The "fixed" code can't run on PHP 4. This strict idea needs a minor > >reevaluation. Using var in PHP 5 isn't really "broken" and in order to > >run code that can run on both 4 and 5 users need to jump through hoops > >and, more importantly, disable the strict checking, which causes them to > >miss REAL deprication problems. > > > >--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 > > > >-- > >PHP Internals - PHP Runtime Development Mailing List > >To unsubscribe, visit: http://www.php.net/unsub.php