rfc:consistent_callables

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_callables [2019/04/28 02:58] danackrfc:consistent_callables [2019/04/28 03:01] danack
Line 225: Line 225:
  
   - A string that is the name of a function.   - A string that is the name of a function.
-  - An array consisting of two elements; a string at index 0 which is a valid fully qualified class name, and a string at index 1 which must meet the conditions+  - An array consisting of two elements; a string at index 0 which is a valid fully qualified class name, and a string at index 1 which must meet the conditionseither be the name of a public static function of the class or the class must have a magic __callStatic method, also the name must not be that of an instance method.
-  * either be the name of a public static function of the class or the class must have a magic __callStatic method.   +
-   +
-  * the name must not be that of an instance method.  +
   - An array consisting of two elements; an object at index 0, and a string at index 1 where either the string is the name of a public method of the object, or the object has a magic __call method.     - An array consisting of two elements; an object at index 0, and a string at index 1 where either the string is the name of a public method of the object, or the object has a magic __call method.  
   - An instance of a class (an object) where the class has a public __invoke() method.   - An instance of a class (an object) where the class has a public __invoke() method.
rfc/consistent_callables.txt · Last modified: 2021/10/20 13:18 by danack