Dan Sugalski wrote:
[ freeze/thaw writer/reader ]
... For this I think we're better off with
specific API functions since the set is small and bounded. If we really
want we can put them in some sort of vtable structure, which might not be
a bad thing.
Sort of vtable could be a real vtable too. I.e.
On Tue, 4 Nov 2003, Leopold Toetsch wrote:
> Dan Sugalski <[EMAIL PROTECTED]> wrote:
> > On Tue, 4 Nov 2003, Leopold Toetsch wrote:
>
> >> Are there already any plans for the frozen image data format?
> >> Currently I'm writing plain ASCII strings, which is quite handy for testing.
>
> > I'd prefe
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> On Tue, 4 Nov 2003, Leopold Toetsch wrote:
>> Are there already any plans for the frozen image data format?
>> Currently I'm writing plain ASCII strings, which is quite handy for testing.
> I'd prefer it to be as dense as possible.
Sure. The ASCII image
On Tue, 4 Nov 2003, Leopold Toetsch wrote:
> Are there already any plans for the frozen image data format?
> Currently I'm writing plain ASCII strings, which is quite handy for testing.
I'd prefer it to be as dense as possible. Besides the format used in
bytecode files (so it'll take up memory sp
Are there already any plans for the frozen image data format?
Currently I'm writing plain ASCII strings, which is quite handy for testing.
The Plan(tm) is to use PBC constant format (or extensions to this)
later, so that PMC constants nicely integrate into byte-code and that
freezing closures can
