| From | Sent On | Attachments |
|---|---|---|
| Charles Oliver Nutter | May 27, 2009 1:08 pm | |
| Martin C. Martin | May 27, 2009 2:46 pm | |
| Nicholas Riley | May 27, 2009 10:58 pm |
| Subject: | Re: JRuby success! | |
|---|---|---|
| From: | Nicholas Riley (njri...@uiuc.edu) | |
| Date: | May 27, 2009 10:58:49 pm | |
| List: | net.java.openjdk.mlvm-dev | |
In article <4A1D...@sun.com>, Charles Oliver Nutter <char...@sun.com> wrote:
The exception-handling logic I'm not sure about. This seems to be a possible gap in primitive method handles: an exception-handling method handle that can wrap another handle with additional logic. I'm not sure exactly how it would manifest itself in the API.
This seems to be a big gap with Jython too. Pretty much all of Jython's lookup and dispatch logic could be done with composed method handles, but exception handling doesn't fit this pattern. The only thing I could think to do for now would be to put the exception logic at the call site, surrounding the invokedynamic; from some benchmarks I did a few months ago it doesn't seem like the overhead is that high.
-- Nicholas Riley <njri...@uiuc.edu>
_______________________________________________ mlvm-dev mailing list mlvm...@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev





