Am 04.02.2012 17:39, schrieb Charles Oliver Nutter:
InvokeBinder is a small Java DSL for binding method handles *forward*
rather than *backward* from target endpoint.
https://github.com/headius/invokebinder/
I've finished mapping MethodHandles.* and Lookup.* to its API, and
have also added a couple convenience utilities like tryFinally and nop
that are hard or confusing to implement with the MethodHandles API.
I'm interested in incorporating other utilities and patterns that you
might have...feel free to submit a pull request.
In general I have till now a bit a problem of keeping the numbers of
method handles low. If I for example have to bind multiple values at
different places in my code, this usually turns out to be multiple
insertArguments calls, each of them producing new method handles. I am
wondering how to avoid that problem
bye Jochen
--
Jochen "blackdrag" Theodorou - Groovy Project Tech Lead
blog: http://blackdragsview.blogspot.com/
german groovy discussion newsgroup: de.comp.lang.misc
For Groovy programming sources visit http://groovy-lang.org
--
You received this message because you are subscribed to the Google Groups "JVM
Languages" group.
To post to this group, send email to jvm-languages@googlegroups.com.
To unsubscribe from this group, send email to
jvm-languages+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/jvm-languages?hl=en.
