rfc:function_referencing
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:function_referencing [2014/08/04 22:55] – Clarity for Danack :) ajf | rfc:function_referencing [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== PHP RFC: Function Referencing as Closures ====== | ====== PHP RFC: Function Referencing as Closures ====== | ||
* Version: 0.1 | * Version: 0.1 | ||
- | * Date: 2014-08-03 | + | * Date: 2014-08-03, latest 2014-08-18, withdrawn 2014-11-03 |
* Author: Andrea Faulds, ajf@ajf.me | * Author: Andrea Faulds, ajf@ajf.me | ||
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
Line 72: | Line 72: | ||
When a function is referenced in this manner, an unbound, unscoped '' | When a function is referenced in this manner, an unbound, unscoped '' | ||
- | Like the [[rfc: | + | We relax the restriction on unbound scoped closures. This is because if we were to give a static method, it could not be bound (useless as it is an instance method), and we don't know what to bind to ahead-of-time. Thus we create an incomplete closure of sorts, which can be called and probably won't work (much like you can statically call an instance method), or can be bound with '' |
Because the '' | Because the '' |
rfc/function_referencing.1407192932.txt.gz · Last modified: 2017/09/22 13:28 (external edit)