rfc:remove_preg_replace_eval_modifier

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
rfc:remove_preg_replace_eval_modifier [2012/02/12 18:28] – Start vote nikicrfc:remove_preg_replace_eval_modifier [2017/09/22 13:28] (current) – external edit 127.0.0.1
Line 3: Line 3:
   * Date: 2012-02-04   * Date: 2012-02-04
   * Author: Nikita Popov <nikic@php.net>   * Author: Nikita Popov <nikic@php.net>
-  * Status: In Draft+  * Status: Implemented
  
 ===== Summary ===== ===== Summary =====
Line 101: Line 101:
 The ''/e'' modifier has little to no valid uses but imposes a rather big security risk. As it can in any case be The ''/e'' modifier has little to no valid uses but imposes a rather big security risk. As it can in any case be
 replaced by a callback there would be no loss in functionality. replaced by a callback there would be no loss in functionality.
- 
-The time line for deprecation and removal is subject to discussion. 
  
 ===== Vote ===== ===== Vote =====
  
-<doodle  +The vote ended with 23 in favor and 4 against the proposal. 
-title="Should the /e modifier be deprecated in trunk?" auth="nikic" voteType="single"> + 
-   * yes +===== Current state ===== 
-   * no + 
-</doodle>+The ''/e'' modifier has been deprecated in trunk in http://svn.php.net/viewvc?view=revision&revision=323862. It will 
 +be removed at some later point in time.
rfc/remove_preg_replace_eval_modifier.1329071281.txt.gz · Last modified: 2017/09/22 13:28 (external edit)

Page Tools