I've added the patch to remove magic quotes from trunk on the RFC. Is there any comments/objection against this patch ?
Pierrick 2010/4/8 Kalle Sommer Nielsen <ka...@php.net>: > Hey Everyone > > I've put together a simple RFC[1] that lists features thats been > deprecated in 5.3, someone of them which I propose we remove in the > next version of PHP, depending on the version number. Most of the > features, which is listed below are taken from the old 6.0 NEWS[2] > file, and items from the old PHP6 TODO[3]. > > safe_mode/register_globals/register_long_arrays/magic_quotes_*/allow_call_time_pass_reference > - Something we have long time been wanted to remove from PHP, I don't > see a big reason to keep those in the next version, even if its going > to be a 5.4, since we already removed things like > zend.ze1_compatibility_mode. See the magic quotes RFC[4]. > > define_syslog_variables and its associated function > - Originally agreed to be removed in PHP6 during the 5.3 development, > if there is no objects then I will remove by the end of this weekend. > > asp_tags > - Proposed to be removed aswell, Tony had a patch for this[5]. > > sql_safe_mode > - Theres currently an RFC in the works about this by Johannes[6]. > > session_register/session_is_registered/session_register > - Only needed for register_globals, Hannes removed those in PHP6. > > enable_dl > - Is this really worth keeping, since dl() was disabled on almost all > SAPIs except for CLI/CGI/Embed? > > Support for Freetype 1 and GD 1 > - Removed by Pierre in PHP6 > > Support for "continue" and "break" operators with non constant operands > - Removed by Dmitry in PHP6. > > Undocumented and incomplete support for strings in list() operator > - Removed by Dmitry in PHP6 aswell. > > detect_unicode/highlight_bg > - Two ini values thats been marked as removed features from PHP6 in > the manual. Not sure about detect_unicode, but highlight_bg is pretty > pointless. > > y2k_compliance > - From the manual "Enforce year 2000 compliance (will cause problems > with non-compliant browsers)", we are in 2010, we should remove this > option and enable it by default and remove the checks. Perhaps Derick > got an insight here? > > Class named constructors > - A feature thats been marked in the manual as something that would > be removed in a future version of PHP6. It was not to be knowing ever > decided to be kept or not, but now with the recent removal of them in > namespaces then I don't see a big point in keeping them. > > > If there is anything I forgot then let me know and I will add it to > the RFC, else discussions away! > > > [1] http://wiki.php.net/rfc/removal-of-deprecated-features > [2] > http://svn.php.net/viewvc/php/php-src/branches/FIRST_UNICODE_IMPLEMENTATION/NEWS?view=markup > [3] http://wiki.php.net/todo/php60 > [4] http://wiki.php.net/rfc/magicquotes > [5] http://marc.info/?l=php-internals&m=117640641605813&w=2 > [6] http://wiki.php.net/rfc/drop_sql.safe_mode > > -- > regards, > > Kalle Sommer Nielsen > ka...@php.net > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
