LS>>
LS>>A while ago someone on IRC suggested that it might be a good idea to add
LS>>"public" to PHP 4.x for forward compatibility. I brought it up again on IRC
LS>>yesterday and several prominent members of the php core community said it
LS>>would be a good idea to add to the 4.4 branch.
Why it would be a good idea? You couldn't run this code on 4.x{x<4}
anymore. And you still don't have php5 capabilities. So you get PHP
code which has all PHP 4 restrictions plus is not portable to arbitrary
PHP 4 version and requires only php 4.4 to run. How is it good?
LS>>I think its a good idea to have, to make it somewhat possible to prepare for
LS>>the PHP5 E_STRICT world, while still developing PHP4 compatible code. I
LS>>could for example see this help increase the PHP5 adoption inside PEAR,
Like, PEAR would drop support for PHP 4.3 or it would have two copies of
the code - one with public keyword and one without?
--
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
