rfc:consistent-names

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:consistent-names [2014/01/22 22:21] yohgakirfc:consistent-names [2021/03/27 14:32] (current) – Move to inactive ilutov
Line 3: Line 3:
   * Date: 2014-01-23    * Date: 2014-01-23 
   * Author: Yasuo Ohgaki, yohgaki@ohgaki.net   * Author: Yasuo Ohgaki, yohgaki@ohgaki.net
-  * Status: Draft+  * Status: Inactive
   * First Published at: http://wiki.php.net/rfc/consistent-names   * First Published at: http://wiki.php.net/rfc/consistent-names
  
Line 18: Line 18:
 Add CODING_STANDARDS compliant name as default name and add legacy name as alias. Add CODING_STANDARDS compliant name as default name and add legacy name as alias.
  
-1) De facto standard names like string operation function (e.g. strcmp()) remains as it is now. +  - De facto standard names like string operation function (e.g. strcmp()) remains as it is now. 
- +  Other names like mb_encode_mimeheader() become alias of mb_encode_mime_header(). 
-2) Other names like mb_encode_mimeheader() become alias of mb_encode_mime_header(). +  Names in question are discussed in internals@lists.php.net 
- +  Aliases are not deprecated and should remain at least next 10 years or more. 
-3) Names in question are discussed in internals@lists.php.net +
- +
-4) Aliases are not deprecated and should remain at least next 10 years or more. +
  
 ===== Backward Incompatible Changes ===== ===== Backward Incompatible Changes =====
Line 44: Line 41:
 ===== New Constants ===== ===== New Constants =====
  
-There may be constants that are better to have better names(?)+There may be constants that may have better names(?)
  
 ===== php.ini Defaults ===== ===== php.ini Defaults =====
rfc/consistent-names.1390429311.txt.gz · Last modified: 2017/09/22 13:28 (external edit)