Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50835
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain edigitalresearch.com does not designate 217.154.180.62 as permitted sender)
To: =?windows-1252?Q?"Christopher_Jones"?= <christopher.jones@oracle.com>
Cc: =?windows-1252?Q?"PHP_Developers_Mailing_List"?=
  <internals@lists.php.net>
Date: Thu, 2 Dec 2010 20:32:47 +0000
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Message-ID: <vmime.4cf8026f.4a00.84353709c1b02fdf@zarafa.edigitalresearch.com>
Subject:  Re: [PHP-DEV] Re: Hold off 5.4
From: james.butler@edigitalresearch.com (=?windows-1252?Q?James_Butler?=)



On 2 Dec 2010, at 19:46, "Christopher Jones" <christopher.jones@oracle.com> wrote:

>=20
>=20
> On 12/02/2010 11:23 AM, James Butler wrote:
>> 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...
>>=20
>=20
> If we decide the next major version doesn't have unicode then we will
> have to manage/expect some community confusion.  This will happen
> regardless of designated version number.
>=20
> Chris

Sorry, I think I misinterpreted what you were saying. You are right, the user expectation will probably need to be managed, irrespective of major version number, for quite a few features that PHP6 was expected to bring, and also any features that will now arrive that are orthogonal to what PHP6 books/media have promised. That said if the next version is 7 / 2011 / whatever, at least it won't return stacks of obsolete and outdated articles, blog posts and books when people start googling it for help and information.

Just my tuppence ha'penny.=20
.
>=20
>> --
>> James Butler
>> Sent from my iPhone
>>=20
>> On 2 Dec 2010, at 19:02, "Christopher Jones"<christopher.jones@oracle.com>  wrote:
>>=20
>>>=20
>>>=20
>>> 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.
>>>=20
>>> 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.
>>>=20
>>> Chris
>>>=20
>>> --
>>> Email: christopher.jones@oracle.com
>>> Tel:  +1 650 506 8630
>>> Blog:  http://blogs.oracle.com/opal/
>>>=20
>>>=20
>>> --
>>> PHP Internals - PHP Runtime Development Mailing List
>>> To unsubscribe, visit: http://www.php.net/unsub.php
>>>=20
>>=20
>=20
> --=20
> Email: christopher.jones@oracle.com
> Tel:  +1 650 506 8630
> Blog:  http://blogs.oracle.com/opal/
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20