I also think we shouldn't backport features to PHP5. We should
(i) keep PHP5 a stable release with a known feature set for developers to use. (ii) have a smaller code base to maintain in PHP5, reducing the overhead of merging. (iii) avoid exacerbating the future situation with uptake of PHP6 vs PHP5 that we now face with PHP5 vs PHP4. Chris Andrei Zmievski wrote: > And I think that we shouldn't, since it removes a big incentive for > people to move to PHP 6. > > Really, we need to get folks to use Unicode natively as much as > possible. It is the way of the future, and not some "obscure feature", > as some here have suggested. This kind of attitude is precisely why > we've had and continue to have such an internationalization mess when it > comes to building applications. > > -Andrei > > > On Jul 6, 2007, at 9:48 AM, Antony Dovgal wrote: > >> On 06.07.2007 20:44, Stanislav Malyshev wrote: >>>> You don't by a Porsche if you need a taxi, why would you install >>>> PHP6 if you don't need Unicode? >>> Namespaces ;) >> This reason is only valid if we don't backport such things from PHP6 >> to PHP5 (5.3, 5.5 or whatever it would be), which I think we should do. >> >> --Wbr, Antony Dovgal -- Christopher Jones, Oracle Email: [EMAIL PROTECTED] Tel: +1 650 506 8630 Blog: http://blogs.oracle.com/opal/ PHP Book: http://tinyurl.com/f8jad -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
