Re: Isolated Methods JEP

Hi Martijn, > Am 09.08.2016 um 00:15 schrieb Martijn Verburg : > Love the overall idea. A few thoughts (feel free to ignore as I'm by no > means an expert in the VM). thank you. As this JEP spans the VM and the libraries, with a definitely client-facing part in MethodHandles.Lookup, user quest

Re: Isolated Methods JEP

Hi Mark, > Am 05.08.2016 um 12:13 schrieb Mark Roos : > Good to see this. thanks. :-) > What is the philosophy for code annotations, line numbers and stack maps? > > Would they be some form of constant entry? I recall you had asked this question at JVMLS. I think it definitely makes sense t

Re: Isolated Methods JEP

Hi Peter, thanks for your feedback! I'm responding to both your messages in one. > Am 09.08.2016 um 05:05 schrieb Peter Levart >: > In the JEP's description you write: > > "The loadCode method creates a method from the passed bytecode instructions > and constants

Re: Isolated Methods JEP

On Aug 12, 2016, at 2:57 PM, Michael Haupt wrote: > > Hi Peter, > > thanks for your feedback! I'm responding to both your messages in one. > >> Am 09.08.2016 um 05:05 schrieb Peter Levart > >: >> In the JEP's description you write: >> >> "The loadCode method crea

Re: Isolated Methods JEP

On Aug 12, 2016, at 2:56 PM, Michael Haupt wrote: > > Hi Martijn, > >> Am 09.08.2016 um 00:15 schrieb Martijn Verburg > >: >> Love the overall idea. A few thoughts (feel free to ignore as I'm by no >> means an expert in the VM). > > thank you. As this JEP span

Re: Isolated Methods JEP

On Aug 12, 2016, at 2:56 PM, Michael Haupt wrote: > > Hi Mark, > >> Am 05.08.2016 um 12:13 schrieb Mark Roos > >: >> Good to see this. > > thanks. :-) > >> What is the philosophy for code annotations, line numbers and stack maps? >> >> Would they be some form of consta