Re: Ruminations on PHP 5++
| From: | Pierre Joye | Date: | Fri, 24 Jan 2014 06:41:28 +0000 |
| Subject: | Re: Ruminations on PHP 5++ | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-71483@lists.php.net to get a copy of this message | ||
hi Adam!
On Fri, Jan 24, 2014 at 7:34 AM, Adam Harvey <aharvey@php.net> wrote:
> Internaleers!
>
> We seem to have a few things being discussed at the moment that are
> somewhat beyond the scope of the sorts of changes we've been adding
> since 5.3. (I think the new release and voting processes have
> generally worked well here, incidentally: 5.4 and 5.5 have both been
> releases with a good range of new features, yet haven't caused
> significant pain in terms of BC and have been pretty stable.) Things
> that fall into that category for me include:
>
> 1. size_t and int changes.
really not going to wait 6 for that. But we have another thread to discuss it.
> 4. Dare I say it, better multibyte encoding handling. (I don't want to
> repeat the PHP 6 experience, but I'm also not sold on mbstring-ng
> being the ultimate solution.)
mbstring-ng and full unicode support can be seen as two different
topics. While some parts overlap.
> So here's my question: should we be starting to lay out a rough
> schedule and list of desired features for a new major release? (I'm
> going to call it 5++, since the actual number is controversial; I'd
> prefer 7, but I know there's a school of thought that 6 is usable
> again. Whatever. We can bikeshed that down the track.)
No way for me, 6 never existed and I see no good reason to skip it
just because we failed to make it happen back then. I'm not in
marketing but tech. Also releasing 6 may actually improve our image.
But releasing it as 7 will make us look like clowns again. Let avoid
that.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org