Differences

This shows you the differences between two versions of the page.

--- rfc:callable [2011/06/07 15:59] – [The problem] weierophinney
+++ rfc:callable [2011/06/16 00:11] – [Previous discussions] stas
@@ Line 1: / Line 1: @@
-====== Request for Comments: How to write RFCs ======
+====== Request for Comments: callable type hint ======
   * Version: 1.0
   * Date: 2011-06-07
@@ Line 34: / Line 34: @@
   * The only arguments against the idea came from Stas, [[http://php.markmail.org/message/hhdjdfo3o34mcj2t?q=callable|making the argument]];
-    * 'callable' are nothing different then 'balanced binary tree' and 'readable file', and none of them make sense to have typehints for.
+    * 'callable' is a data structure not unlike 'balanced binary tree' and 'readable file', and none of them make sense have as a part of the language syntax. They belong in userspace.
-    * A "strict typing error" is hard to handle in user-space gracefully
+    * A "strict typing error" is hard to handle in user-space gracefully.
-  * Everyone else seem to like the idea.
+  * Everyone else seem to like the idea, so far.
   * As for the patch itself, Felipe pointed out that the patch is missing an method in ext/reflection to retrieve the typehint information.
+  * Things to finalize:
+    * Type name: documentation uses 'callback', not 'callable' as proposed
+    * Are initializers allowed?
+    * Does validation include visibility, as is_callable() does?
+    * Reflection support
+    * Arginfo support