Am 30.07.2013 17:58, schrieb Charles Oliver Nutter: [...] > Third, for language runtimes like Groovy, it seems to me that only > *effort* is required to handle the passing down of the caller class. > If we look at the facts, we see that getCallerClass is needed to skip > intermediate frames by the runtime. So the runtime knows about these > intermediate frames and knows how many to skip.
knowing how many frames to skip where? In the target method? no. At the end of the path, just before the method call? sometimes, depends on the path. But since the information is lost there it does not matter > This means that the > original call is not into an uncontrolled library, but instead is into > Groovy-controlled code. Passing down the caller object or class at > that point is obviously possible. Even if the hassle of passing a new > additional parameter through the call protocol is too difficult, a > ThreadLocal could be utilized for this purpose. And what will hotspot say here? 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 _______________________________________________ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
