Are there restrictions on the 'name' string for invokeDynamic?

Ola Bini ola.bini at gmail.com
Fri Apr 15 06:09:45 PDT 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2011-04-15 02.25, Mark Roos wrote:
> I ran into this error today and was wondering if "<" was not allowed as
> the name string for an invokeDynamic instruction?
> 
> An if there are restrictions where might I find the definitive
> reference?  I was using it for the Smalltalk method name and
> as a template for constants.  
> 
> Thanks
> mark

Hi Mark,

If I remember correctly, the same restrictions for method names in byte
code applies for the name as for all other method names. I handled this
by using John Rose's name mangling class more or less directly
(http://blogs.sun.com/jrose/entry/symbolic_freedom_in_the_vm  and
http://blogs.sun.com/jrose/resource/StringNames.java.txt). I then encode
the name before compiling it and then decode it in the bootstrap method.

Cheers
- -- 
 Ola Bini (http://olabini.com)
  Ioke - JRuby - ThoughtWorks

 "Yields falsehood when quined" yields falsehood when quined.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJNqEOUAAoJEClcdGmEr38M/Y4QAMpS2eZ8FrFKtbnFD7nzyTds
GGHy1SsMm5rbVrp6PkFjer2SWu4OoKhIXijull4llFd8eZLsbpk8JGPX9ACLyZCs
azPfdUuRnclPYLjPjeUsGtfOvdBB9lhGE/8ftD3KR8RpnPgwzLlivaTkE+up9OL4
9zwtBnsSd44220GLNZYyVBcHD3jm3HDxUebPr1LFapZVZvrEOsi8C78OMj6djTo0
dLyingBQrGhGq5Wt00s6qPtnIohbPD8qcVtnd3Cb+MljB9x0jOqQrpcd5nQALQvV
vcox9oktalTzk5yGIWP2qqtnoXLnejFgOomZF2m4ypA3zXKi6BzJ7ZjKjKmYQBBX
ywNpAg4270bU04sTiVCSGHXeOngxR3tjusG0lyanZOOeweb48nXKgAA3RfOhTu5j
IO5MSyXLpBfVfPihx2mCmL3R2E56YuDPdHHNbcSGH+gNxCB2h+P1hIhW1QylVj75
Z5uWHjj830cUv5tMW5Me28e29lPnfOxMplma+CpIC8hhf5sIFpcTGVz/zF5uy2iu
x8q7xq9ksgqBtp8rxVfvU0fcyTktlynW0Avs1O4zBNeDbefg1pTOeszOYaPNbFXB
8MvDilg0SFGDyTt+TyTpGfshbnbAb0rT0hrh4UoS95ZBlBpGtNFS4hZ4enWPLVeC
OGqRxK8yid9+SuBpv4Bb
=IC9E
-----END PGP SIGNATURE-----


More information about the mlvm-dev mailing list