Re: forward compatibility "public" in 4.4

Stanislav Malyshev wrote: > SM>>IMHO is 'var' the only thing that produces NOTICES in PHP 5 what can > SM>>not be changed if this app should run in both Versions 4 and 5, > SM>>others, like '= new' and '=& new' can easily be adopt by just > SM>>removing > SM>>the '&' without getting any NOTICE in any VERSION > > Here's something I am missing - if you say notices are so much rpoblem, > why not remove them? oh, PHP introduced NOTICEs so that i remove them? great ... > SM>>i think 'var' is the most important reason for the current delay in the > SM>>move to PHP 5! > > Eh? Why is that? Is it so hard to write one one-line script that would > replace ALL vars to publics? no but this so changed app could not run on both versions at the current state i can run one Server with both versions, accessing with different virtual hosts the same script ones interprated by PHP 5 and on the other vhost with PHP 4, but with Notices enabled i get overhelmed by 'var is deprecated' > SM>>i would even go a step further: > SM>> > SM>>-<ST_IN_SCRIPTING>"var" { > > SM>>SM>>+<ST_IN_SCRIPTING>("var"|"public"|"private"|"protected") > SM>>{ > > Ouch. So you could write code that would run on PHP4 perfectly well and > break on PHP5? this can be done already, just to mention overwriting $this, or changing a copy of an object in PHP 4 changes the original object in PHP 5 also, this all three are 'silent' changes - that reports no errors but can break the app but this are all errors that can be fixed without getting notices in both versions but work in both versions -- Sebastian Mendel www.sebastianmendel.de www.sf.net/projects/phpdatetime | www.sf.net/projects/phptimesheet