On Aug 4, 2016, at 9:11 AM, Mark Roos <mr...@roos.com> wrote:
> 
> With respect to general data in constant pools 
> 
> Adding raw bytes as a constant type would be a good thing.  I currently 
> have to encode my object serialization as hex utf8 which is not nice. 

+1

> As for the use of a MH to instantiate the constant.  Would this be done 
> at load time or would it just insert a ConstantCallSite to instantiate at 
> run time ( lazy )?  My two concerns would be that not everything is in 
> place at load time and the creation of lots of large constants which are 
> never used. 

The constant would be expanded when it is resolved, on first use.
That's the usual semantics for constants (like CONSTANT_MethodHandle).
So unused constants won't take up any space beyond their dormant
symbolic references.

— John
_______________________________________________
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev

Reply via email to