rfc:my_rfc

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
rfc:my_rfc [2015/01/31 00:53]
yohgaki
rfc:my_rfc [2015/01/31 00:59]
yohgaki
Line 9: Line 9:
  
 There are number of INI set/get functions. This RFC proposes deprecation of these functions. There are number of INI set/get functions. This RFC proposes deprecation of these functions.
 +
 +Use of ini_set()/​ini_get() simplifies/​improves/​cleanups PHP. Some of these alias function names is inconsistent,​ some aliases are missing while similar INI setting may be set/get by aliases. Simple INI set/get alias functions are just making PHP complex, creating more inconsistencies. PHP needs no more INI set/get aliases at least, document use of ini_get()/​ini_set() in the CODING_STANDARDS.
 +
  
 **Pros** **Pros**
Line 35: Line 38:
 ini_set('​display_errors',​ '​Off'​);​ ini_set('​display_errors',​ '​Off'​);​
 ini_set('​default_charset',​ '​UTF-8'​);​ ini_set('​default_charset',​ '​UTF-8'​);​
-mbstring_internal_encoding('​UTF-8'​);​+mb_internal_encoding('​UTF-8'​);​
 </​code>​ </​code>​
  
Line 68: Line 71:
 ===== Proposal ===== ===== Proposal =====
  
-Use of ini_set()/​ini_get() simplifies/​improves PHPPHP needs no more INI set/get aliases at least, document use of ini_get()/​ini_set() in the CODING_STANDARDS. +There are 2 documentation and 1 code change proposal 
  
 1. Add plain ini_get/​set() usage in **CODING_STANDARDS**. In the "Code Implementation"​ session add following standard. 1. Add plain ini_get/​set() usage in **CODING_STANDARDS**. In the "Code Implementation"​ session add following standard.
rfc/my_rfc.txt · Last modified: 2017/09/22 13:28 (external edit)