Following that logic, they will expect the next major version number, whatever it is, to have Unicode. Nothing can be done about that apart from telling the world it won't, including it in, or let them find out for themselves...
-- James Butler Sent from my iPhone On 2 Dec 2010, at 19:02, "Christopher Jones" <christopher.jo...@oracle.com> wrote: > > > On 11/26/2010 11:15 AM, Zeev Suraski wrote: >> 3. The motivation to skip 6 doesn't stem from marketing at all. The main >> motivation is that there's a VERY concrete perception amongst many users >> about what PHP 6 is. It's unlikely that PHP 6 will actually be that. >> Skipping this version makes perfect sense from just about any POV I can >> think of. That's actually one thing I do feel more strongly about - we >> should probably not reuse the version number 6.0 for something that's >> completely different than what we've been talking about for several years, >> whether it's now or anytime in the future. > > Users aware of PHP 6's unicode intentions will assume PHP 7 is a superset of > PHP 6 and therefore has unicode. So skipping the number "6" won't resolve > any user confusion. > > Chris > > -- > Email: christopher.jo...@oracle.com > Tel: +1 650 506 8630 > Blog: http://blogs.oracle.com/opal/ > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
