Re: quick polls for 5.3
| From: | Elizabeth M Smith | Date: | Wed, 12 Nov 2008 19:55:44 +0000 |
| Subject: | Re: quick polls for 5.3 | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-41875@lists.php.net to get a copy of this message | ||
[snip]
> 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 (go ahead, let them shoot in foot)
> 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 to both (don't care)
> 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
Thanks,
Elizabeth Smith