Re: quick polls for 5.3

hi Lukas! Thanks for this nice little list, 1st class troll killer :) On Wed, Nov 12, 2008 at 8:14 PM, Lukas Kahwe Smith <mls@pooteeweet.org> wrote: > 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) > 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? 0 > 5) keep ext/sqlite3 enabled by default in 5.3? +1 > 6) enable mysqlnd by default in 5.3? (answer both) > II) also enable ext/mysql, mysqli und pdo_mysql by default since there will > be no external dependencies in this case +1 > 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 (if it creates non fixable issues during the alpha/RC phases, it can always be reverted. However the code is much cleaner and easier to maintain, if I can use the word "easy" for the OB code) > 8) MFH mcrypt cleanups in HEAD. either the make sense or they dont, so > either (choose one) > b) MFH to 5.3 +1 (there is tests, there is people taking of it if there are issues, more tests can be added as wish, it removes duplicate codes) Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org