> There's a one-off conversion penalty at bytecode load time, and I don't > consider that excessive. I want the bytecode to potentially be in platform > native format (4/8 byte ints, big or little endian) with a simple and > well-defined set of conversion semantics. That way the bytecode loader can > manage it quickly, and the external conversion tool (To change between > types) can deal with it simply as well. If you want native format, you have implement runtime specific image file format, such as Smalltalk image. It will be hard to use one format for both native and portable. Hong
- Re: RFC: Bytecode file format Jarkko Hietaniemi
- Re: RFC: Bytecode file format Gregor N. Purdy
- RE: RFC: Bytecode file format Hong Zhang
- RE: RFC: Bytecode file format Dan Sugalski
- Re: RFC: Bytecode file format Benjamin Stuhl
- RE: RFC: Bytecode file format Brent Dax
- Re: RFC: Bytecode file format Brian Wheeler
- RE: RFC: Bytecode file format Hong Zhang
- Re: RFC: Bytecode file format Jarkko Hietaniemi
- Re: RFC: Bytecode file format Benjamin Stuhl
- Re: RFC: Bytecode file format Hong Zhang
- Re: RFC: Bytecode file format Jarkko Hietaniemi
- Re: RFC: Bytecode file format Jarkko Hietaniemi
- Re: RFC: Bytecode file format Jarkko Hietaniemi
- Re: RFC: Bytecode file format Damien Neil
- Re: RFC: Bytecode file format Dan Sugalski
- Re: RFC: Bytecode file format Jarkko Hietaniemi
- Re: RFC: Bytecode file format Jarkko Hietaniemi
- Re: RFC: Bytecode file format Damien Neil
- Re: RFC: Bytecode file format Dan Sugalski
- Re: RFC: Bytecode file format Damien Neil