On Fri, Jun 10, 2011 at 6:32 PM, Charles Oliver Nutter <head...@headius.com> wrote: > The post logic is another story. I can handle the finally in general > with MethodHandles.catchException, but I can't call post() and then > continue to propagate the return value of someOtherCall(). Even worse, > because of the issue in my other thread, I can't insert a > non-exceptional call to post() after someOtherCall() if it needs to > receive arguments (because filterReturn doesn't get arguments).
Sorry, I made a mistake here. What I should have said: I can handle the exceptional case with MethodHandles.catchException ok. There's no return value because an exception was thrown, so I just do the post logic and propagate the exception. But I can't handle the non-exceptional case; there's no way to do post-processing of a call. What I really need is something like: MethodHandles.postProcess(mh, post) where the "post" handle will receive the incoming arguments AND the result of the call and decide what to return. Of course I would discover this in June, right after high resistance for Java 7 :( - Charlie -- 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.
