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 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?

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?

SM>>i would even go a step further:
SM>>
SM>>-<ST_IN_SCRIPTING>"var" {
SM>>+<ST_IN_SCRIPTING>("var"|"public"|"private"|"protected") {

Ouch. So you could write code that would run on PHP4 perfectly well and 
break on PHP5? 
-- 
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED]  http://www.zend.com/ +972-3-6139665 ext.115

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to