Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41869
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.200.173 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=V+eqJ9yfacoLp5V/kr7GfNxTjMS2tblDAMlruC67dnhJzPAp3ZWRIkoku0b/2PlS0S
         FbJqArd7uRIcU2mfk85p6wVLgID73q6HYCaDhXmGhk00pa38/P55nIIgoWT4u00vLTMV
         8f+ik9T/62v6H0dG3xw4UwEtW1RYld3kQBsc4=
Message-ID: <b5f7bf6c0811121125q3c03f229yab90c4f2abade24@mail.gmail.com>
Date: Wed, 12 Nov 2008 19:25:58 +0000
Sender: david.coallier@gmail.com
To: "Lukas Kahwe Smith" <mls@pooteeweet.org>
Cc: "internals Mailing List" <internals@lists.php.net>
In-Reply-To: <42D56477-0E39-4548-B711-A950480E562E@pooteeweet.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <42D56477-0E39-4548-B711-A950480E562E@pooteeweet.org>
Subject: Re: [PHP-DEV] quick polls for 5.3
From: davidc@php.net ("David Coallier")

> 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

+1

> II) remove ext/mhash

+1

> 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

+1

> 3) resource constants (choose one)
> c) Document as is

+1

> 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

I'd say personally +1 because I have it enabled everywhere already but
thinking in a larger user base where not everyone is using mysql I
have to say -1

> II) also enable ext/mysql, mysqli und pdo_mysql by default since there will
> be no external dependencies in this case

+1 if it ends up turned on by default, -1 otherwise.

> 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

> 8) MFH mcrypt cleanups in HEAD. either the make sense or they dont, so
> either (choose one)
> b) MFH to 5.3

+1


-- 
Slan,
David