Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41909
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.94.56 as permitted sender)
Date: Thu, 13 Nov 2008 20:46:38 +0100
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <1118152645.20081113204638@marcus-boerger.de>
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>
References: <42D56477-0E39-4548-B711-A950480E562E@pooteeweet.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] quick polls for 5.3
From: helly@php.net (Marcus Boerger)

Hello Lukas,

Wednesday, November 12, 2008, 8:14:31 PM, you wrote:

> Hi,

> here are a few questions that need to be answered ASAP.

> If at all possible keep your votes as short as possible. I think all  
> of the above topics have been discussed quite a lot on the list. So I  
> hope voters can spare the list needless repetition. Instead if you  
> think that a topic needs to be discussed, put a short note in your  
> vote under the given topic. If a number of people also think the topic  
> needs more discussion, then we can open a new thread dedicated to this  
> topic later this week.

> 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)
> 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
"c"

> 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

> 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
+1

In short, MFH what we can, keep at least one DB in PHP per default.
Enable all by default that does not depend on any library or move to
PECL. Introduce stuff to core, enabled by default that we develop for
mainstream usage. Do not do unneccessary changes, clarify docs always.
And last but not least adhere to KISS and consistency.

> regards,
> Lukas Kahwe Smith
> mls@pooteeweet.org







Best regards,
 Marcus