You can already get an array of StackTraceElements, each of which can give you the Method that was invoked....
I take it you want *mutable* access to the stack? Ted Neward Java, .NET, XML Services Consulting, Teaching, Speaking, Writing http://www.tedneward.com > -----Original Message----- > From: [email protected] [mailto:jvm- > [EMAIL PROTECTED] On Behalf Of Don Schwarz > Sent: Tuesday, January 08, 2008 9:30 AM > To: [email protected] > Subject: [jvm-l] Re: A better solution for artificial call frames? > > > On Jan 7, 2008 7:24 AM, Kresten Krab Thorup <[EMAIL PROTECTED]> wrote: > > > > Another aspect is, that frames are the only kind of object reference > > source which is not accessible by reflection. Having some kind of > > reflective access to this would allow several new behaviors in the > > meta layers. > > > Agreed. > > Even just being able to get a stack of Method objects for a thread > would be useful in many situations, especially when tied to reflection > of Method annotations. > > > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.516 / Virus Database: 269.17.13/1214 - Release Date: > 1/8/2008 1:38 PM > No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.17.13/1214 - Release Date: 1/8/2008 1:38 PM --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
