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
Next revisionBoth sides next revision
rfc:consistent-names [2014/01/22 22:05] – yohgakirfc:consistent-names [2014/01/22 22:21] – yohgaki
Line 8: Line 8:
 ===== Introduction ===== ===== Introduction =====
  
-PHP has been developed about 20 years. Many legacy functions/methods does not comply CODING_STANDARDS "Naming Conventions".+PHP has been developed about 20 years. Many legacy functions/methods do not comply CODING_STANDARDS "Naming Conventions".
  
 Inconsistent names are not appealing for new users. Having consistent names would help to assure PHP's attractiveness to learn. Older names should be usable for compatibility. Inconsistent names are not appealing for new users. Having consistent names would help to assure PHP's attractiveness to learn. Older names should be usable for compatibility.
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 like strcmp() remains as it is now.+1) De facto standard names like string operation function (e.g. strcmp()) remains as it is now.
  
 2) 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().
rfc/consistent-names.txt · Last modified: 2021/03/27 14:32 by ilutov

Page Tools