Re: data storage and representation when designing bytecode (and VM)

2000-10-04 Thread John van V
> >The knowledge gathered from writing the modules Storable, > >Freeze::Thaw, and Data::Dumper, should be studied very carefully. Those are my lifeblood, that's why I proposed having them in the core as being key to persistance and communication. I store in binary and communicate with Data::D

Re: data storage and representation when designing bytecode (and VM)

2000-10-02 Thread Jarkko Hietaniemi
> 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

Re: data storage and representation when designing bytecode (and VM)

2000-10-02 Thread Nicholas Clark
On Mon, Oct 02, 2000 at 04:35:29PM -0400, Dan Sugalski wrote: > 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

Re: data storage and representation when designing bytecode (and VM)

2000-10-02 Thread Dan Sugalski
At 07:21 AM 10/2/00 -0500, Jarkko Hietaniemi wrote: >[random thoughts I had one week ago at YAPC::Europe and am jotting down now; > was unsubscribed from the p6 lists during that time, awfully sorry if this > subject has already been beaten to death] We haven't touched this yet. Bytecode's on t