Stanislav Malyshev wrote:
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?
Currently PEAR.php requires PHP 4.2.
We could eventually (as an intermediate step) move this dep to 4.4, not
immediatly. However currently there is a strong trend to create new
versions of packages for the main reason of making them E_STRICT
compatible. However lets not get too far into the PEAR politics here ;-)
Anyways I just wanted to give this as an example. I think its much more
useful for independent developers who have more control over their user
setups than PEAR. This allows them to make the move less painful and
therefore will facilitate rather than prolong the move to PHP5 (which is
a good thing).
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
