LS>>Currently PEAR.php requires PHP 4.2. This means there are a lot of people using PEAR with PHP 4.3 and 4.2. And there's almost no people using it with 4.4 - since 4.4 is not out. So now you want to go out and tell them "upgrade your hosting to our brand-new PHP version risking breaking existing apps - or lose PEAR. And it's all because we want a fancy keyword". Not a good message for a package that should be to PHP something like libc is to C, I think.
LS>>Anyways I just wanted to give this as an example. I think its much LS>>more useful for independent developers who have more control over LS>>their user setups than PEAR. This allows them to make the move less LS>>painful and therefore will facilitate rather than prolong the move to LS>>PHP5 (which is a good thing). I wonder what was the original purpose of PHP5 emitting warning when seeing 'var'? What are you basically saying now is "I want PHP4 code that wouldn't have messages on my class vars if run in PHP5". But I'm sure there was some idea behind these warnings, not? -- 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
