> Yep, that's something to investigate. I'd like to encode the bytecode
> version at the head of any bytecode stream. There's also been a request for
This version info could quite naturally live in my proposed 'declaration
block' or 'bytecode header'.
> I agree, platform native is a good idea generally, as long as we have some
> means of indicating how the platform encodes the data. The bytecode needs
> to be transportable across platforms--I want the same bytecode to be able
> to run on a VAX, x86, Alpha, and PowerPC box.
I agree on your agreement.
> Also, transportable floats are rather problematic. It's one thing to tag an
> integer with size and endianness. It's rather another to deal with floating
> point formats. I have at least six available to me on my Alpha box, and who
> knows how many elsewhere. I'd rather not have to have code to deal with all
Ouch, too true...
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
