| Issue 8: | why Invoker? | |
| 1 person starred this issue and may be notified of changes. | Back to list |
I'm not sure I understand the value of Invoker. It seems that Invoker: (a) translates from apply() to invoke() (b) translates from Throwable to FuncitoEx I wonder if Invokable should have an apply() method in the interface and/or expect implementations to catch Throwable. Admittedly, Invokable.apply() seems a bit odd, esp. if it becomes the primary method. So, that leads me to wonder if it should be named Applicable. Alternatively, if we ignore (a) above but strive for (b), perhaps the outer objects such as MethodFunction should hold an Invokable and call invoke().
Nov 20, 2011
Project Member
#1
kandpwel...@gmail.com
Status:
Accepted
Nov 22, 2011
(No comment was entered for this change.)
Status:
Started
Nov 22, 2011
Fixed. Feel free to review
Status:
Fixed
Nov 22, 2011
(No comment was entered for this change.)
Labels:
Priority-Medium Maintainability
|