Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41881
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 72.14.220.154 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=bNOC0g+WDrJymk+fZa3mVvyioDaqrGExYYOt7HqdEXKM1+NdlrvTtpFbhIt8t6Ehot
         QMsMz3xxMt6Z608TgaDsbWwqk244d1IRAuwuHDtiRwPHGfsSLilfwcVZUSi5jrbM1QEl
         lGMHCoASvnoAjVm67ssAKOC4OQE+pw5Xp6ChU=
Message-ID: <2dedb8a0811121239i16b09303kf2bcc9945a0b3d69@mail.gmail.com>
Date: Wed, 12 Nov 2008 21:39:14 +0100
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=ISO-8859-1
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: kalle.php@gmail.com ("Kalle Sommer Nielsen")

> 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
+0

>
> 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

>
> 3) resource constants (choose one)
> a) Should we deprecate constant resources (mostly used to emulate STDIN and
> friends)
> b) Should we instead just throw an E_STRICT
> c) Document as is
b

>
> 4) keep ext/phar enabled by default in 5.3?
+1

>
> 5) keep ext/sqlite3 enabled by default in 5.3?
+0

>
> 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
+1 on both

>
> 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)
> a) revert in HEAD
> b) MFH to 5.3
+0



-- 
Kalle Sommer Nielsen