Re: constant-dynamic specification, updated

2017-06-25 Thread Remi Forax
> De: "John Rose" > À: "Per Bothner" > Cc: "Da Vinci Machine Project" > Envoyé: Lundi 26 Juin 2017 00:21:58 > Objet: Re: constant-dynamic specification, updated > On Jun 25, 2017, at 3:00 PM, Per Bothner < p...@bothner.com > wrote: >

Re: constant-dynamic specification, updated

2017-06-25 Thread John Rose
On Jun 25, 2017, at 3:00 PM, Per Bothner wrote: > > That will be difficult as long as constant pool indexes and various > other fields are limited to 16 bits. Yep; that's a challenge, until we break the glass and make a completely new class file format that integrates a var-int format. (My favor

Re: constant-dynamic specification, updated

2017-06-25 Thread Per Bothner
On 06/25/2017 02:34 PM, John Rose wrote: My overall goal is to keep the classfile alive as an efficient medium for more and more advanced language runtimes. That will be difficult as long as constant pool indexes and various other fields are limited to 16 bits. -- --Per Bothner p...@bo

Re: constant-dynamic specification, updated

2017-06-25 Thread John Rose
On Jun 25, 2017, at 12:47 PM, Mark Roos wrote: > > I was looking for boot strap args to allow byte[] constants from the > constantPool. > > Is that planned? Yes; there are two more CP types planned: 1. CONSTANT_Data = arbitrary blob of octets 2. CONSTANT_Group = series of constant specifier