Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41877
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.116 as permitted sender)
Message-ID: <491B366C.9010603@zend.com>
Date: Wed, 12 Nov 2008 12:02:52 -0800
Organization: Zend Technologies
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Lukas Kahwe Smith <mls@pooteeweet.org>
CC: internals Mailing List <internals@lists.php.net>
References: <42D56477-0E39-4548-B711-A950480E562E@pooteeweet.org>
In-Reply-To: <42D56477-0E39-4548-B711-A950480E562E@pooteeweet.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] quick polls for 5.3
From: stas@zend.com (Stanislav Malyshev)

Hi!

> 1) ext/mhash in 5.3. ext/hash has all the functions, so the entire BC 
> break will be that "if (extension_loaded('mhash'))" will need fixing if 
> mhash is removed (answer both)
> I) enable ext/hash by default
> II) remove ext/mhash

I) +1
II) Can't we make mhash "stub" extension with dependency on hash so only 
thing you get when you load it is that extension_loaded is OK and no BC 
break? Dependency would ensure the functions are there, and we get the 
bets of both worlds.

> 2) deprecate ereg*. ext/ereg is an extension as of PHP 5.3. Since 
> ext/ereg is more or less redundant with ext/preg and is likely to not 
> get much unicode love for PHP 6, the question is if we should mark it 
> with a E_DEPRECATED in PHP 5.3

-0.5
I'd say not yet, but don't care too much.

> 4) keep ext/phar enabled by default in 5.3?

+1

> 5) keep ext/sqlite3 enabled by default in 5.3?

+1

> 6) enable mysqlnd by default in 5.3? (answer both)
> I) enable mysqlnd by default
> II) also enable ext/mysql, mysqli und pdo_mysql by default since there 
> will be no external dependencies in this case

0

> 7) should Output buffering rewrite MFH? this one comes with some 
> baggage, we need enough people to actually have a look at how things are 
> in HEAD and make it clear that they will be available for bug fixing and 
> BC issues resolving. the risk here is obviously that any BC issues will 
> be hard to isolate for end users.

-1 for now
Need more explanation why we need rewrite, what the rewrite does, etc. 
If there's a good reason and maintainer, then maybe +1.

> 8) MFH mcrypt cleanups in HEAD. either the make sense or they dont, so 
> either (choose one)
> a) revert in HEAD
> b) MFH to 5.3

Same as above.
-- 
Stanislav Malyshev, Zend Software Architect
stas@zend.com   http://www.zend.com/
(408)253-8829   MSN: stas@zend.com