Hi Lester, Lester Caine wrote: > While I have loaded 5.3.? changing any of my existing code base to > remove warnings is not likely to happen any time soon since > compatibility with users who are still running older versions of PHP > still needs to be maintained. > > I've got http://wiki.php.net/doc/scratchpad/upgrade/53 which seems to be > currently the only reference to changes? But where do I find the detail > on how things ARE currently implemented such as namespace and (fingers > down throat) goto?
the manual is ridiculously up to date, and is the best reference location for new features. Occasionally things are documented within seconds of commit and in one case *prior* to commit. It's frightening what they do :). > Another major concern here since maintaining BC with *PHP4* is still an > unfortunate current requirement in the field is what happens when PEAR > actually uses namespace and other 5.3 only features. HOW will we manage > accessing versions of PEAR that are compatible with our active codebase > and so ensure that we have compatible sets of packages? This and the following paragraph are questions for PEAR, and don't concern internals developers, [EMAIL PROTECTED] is the best list for tech questions like the ones you raise. However, I will say that PEAR has been doing just fine with the handling of PHP version differences to date. The installer is fully aware of PHP version dependency, and refuses to install packages that are incompatible with your PHP version. If you find an older package that has an incompatibility with a newer PHP version, this is considered a bug in the package that must be fixed (again, a PEAR problem, not a PHP problem). However, if you upgrade PHP, it is best to upgrade the existing packages to be sure you have ones compatible with the current PHP release. This is a tricky problem, but fortunately the most-used PEAR packages are carefully tracked against PHP releases by their maintainers, so we have not had a PHP version-related problem since the move to 5.0. > Personally I can't stand the CURRENT problems that is caused by not > knowing which version of a PEAR extension users actually have and in > order to ensure a COMPATIBLE version, but in future will the PEAR > installer pick up a correct version for the copy of PHP actually being run? "pear list" show the version information you need, and PEAR since version 1.6.0 takes into account PHP version prior to download (1.6.0 was released June 7, 2007) > I get the distinct impression that those pushing for PHP5.3 are simply > not making a good case for many of us to even want to follow them down > that path? It almost feels like this is a DIFFERENT path to the main > stream of PHP6 which many of us are much more desperate to be testing in > the field, which seems to have become an ignored backwater? Key elements > which have been flagged to PHP6 ( such as BIGINT ) are on hold while new > concepts which were not part of the PHP6 reoadmap have been forced > through? Since current hardware *IS* 64 bit, actually handling 64 bit > numbers properly would be nice :) I think I have made an excellent case for the things that I care about in 5.3. ;) Greg -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
