Closed GoogleCodeExporter closed 9 years ago
In the previous post, it was supposed to say "In *Jedi* it is Command..."
Original comment by kandpwel...@gmail.com
on 18 Aug 2012 at 7:59
Was going to attempt this as it seemed trivial, but ran into major roadbloack:
http://stackoverflow.com/q/12136381/433348
(short version: Command or Effect would likely wrap void methods that produce
*only* side effects, but can't use a call to a void method as argument to a new
Funcito method).
Original comment by kandpwel...@gmail.com
on 28 Aug 2012 at 3:50
Original comment by kandpwel...@gmail.com
on 7 Mar 2013 at 3:18
Also, in Collections-generic (generic version of apache commons collections),
the "command"-like class would be Closure:
https://github.com/megamattron/collections-generic/blob/master/src/java/org/apac
he/commons/collections15/Closure.java
Original comment by kandpwel...@gmail.com
on 4 Jun 2013 at 4:07
Looks like I will implement this despite previously mentioned "roadblock". API
will use "typical" Funcito semantics for method calls that are not-null (even
though return value will be ignored). And for void method-calls (sadly) users
will have to use a 2-line semantic to initialize a Command/Effect/Closure.
Original comment by kandpwel...@gmail.com
on 6 Jun 2013 at 3:05
Original comment by kandpwel...@gmail.com
on 6 Jun 2013 at 3:07
comment 5 was supposed to say "non-void" rather than "not null"
Original comment by kandpwel...@gmail.com
on 14 Jul 2013 at 7:18
Original comment by kandpwel...@gmail.com
on 17 Jul 2013 at 3:42
Original comment by kandpwel...@gmail.com
on 31 Oct 2013 at 6:19
Original issue reported on code.google.com by
kandpwel...@gmail.com
on 19 Jul 2012 at 9:06