rfc:shortsyntaxforfunctions
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
rfc:shortsyntaxforfunctions [2011/06/01 13:25] – created tony2001 | rfc:shortsyntaxforfunctions [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Request for Comments: | + | ====== Request for Comments: |
* Version: 1.0 | * Version: 1.0 | ||
* Date: 2011-06-01 | * Date: 2011-06-01 | ||
Line 8: | Line 8: | ||
- | This RFC is a parody on shortsyntaxforarrays RFC. | + | This RFC is a parody on [[https:// |
===== Introduction ===== | ===== Introduction ===== | ||
Line 15: | Line 15: | ||
The purpose of RFCs are to work collaboratively towards a specification and finally an implementation of an idea. | The purpose of RFCs are to work collaboratively towards a specification and finally an implementation of an idea. | ||
- | ==== Why do we need RFCs? ==== | + | ===== Syntax ===== |
- | They serve to keep a summary | + | We might just replace the current **function < |
+ | I'd personally propose | ||
- | ===== Syntax ===== | ||
- | We might just replace the current function | + | Example code: |
- | I'd personally propose to use dots for everything of the above. It' | + | |
+ | <code php> | ||
+ | function some_long_function_name($array_parameter_omg, | ||
+ | { | ||
+ | | ||
+ | } | ||
+ | </code> | ||
+ | |||
+ | New short non-ugly easily readable example code: | ||
+ | <code php> | ||
+ | . .[., .]. | ||
+ | . | ||
+ | | ||
+ | . | ||
+ | </ | ||
===== Proposal and Patch ===== | ===== Proposal and Patch ===== | ||
Line 30: | Line 44: | ||
===== Changelog ===== | ===== Changelog ===== | ||
- | 2011-06-01 Initial revision. | + | - 2011-06-01 : Changed the RFC to include dashes. |
+ | - 2011-06-01 |
rfc/shortsyntaxforfunctions.1306934756.txt.gz · Last modified: 2017/09/22 13:28 (external edit)