Re: Draft JEP: Efficient Stack Walking API

2014-07-09 Thread Remi Forax
On 07/09/2014 03:42 PM, David M. Lloyd wrote: Just want to say that I am also looking forward to progress on this. so am i :) Rémi On 07/09/2014 12:25 AM, Jeremy Manson wrote: Thanks for the response, Mandy. I'm looking forward to seeing the final version. For CallerFinder, we use refle

Re: Draft JEP: Efficient Stack Walking API

2014-07-09 Thread David M. Lloyd
Just want to say that I am also looking forward to progress on this. On 07/09/2014 12:25 AM, Jeremy Manson wrote: Thanks for the response, Mandy. I'm looking forward to seeing the final version. For CallerFinder, we use reflective goop to get at sun.misc.JavaLangAccess.getStackTraceElement. I

Re: Draft JEP: Efficient Stack Walking API

2014-07-08 Thread Jeremy Manson
Thanks for the response, Mandy. I'm looking forward to seeing the final version. For CallerFinder, we use reflective goop to get at sun.misc.JavaLangAccess.getStackTraceElement. It requires us to build a Throwable (with associated stacktrace), but not to generate all of those StackTraceElement[]

Re: Draft JEP: Efficient Stack Walking API

2014-07-07 Thread Mandy Chung
Hi Jeremy, Thanks for the feedback and the CallerFinder API you have. On 7/7/2014 9:55 AM, Jeremy Manson wrote: Hey folks, I don't know if Mandy's draft JEP has gotten any love, The JEP process is in transition to 2.0 version. Hope this JEP will come out soon. but this is something that