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 prefer it to be as dense as possible.
>
> Sure. The ASCII image is for testing/debugging only. The questions was,
> if a PBC-like format is ok.
I'll have to go look at the pbc format and see. Probably, though.
> >> typedef struct _visit_info {
> >> ...
> >> push_item_f push_item; /* write item to image */
> >> shift_item_f shift_item; /* get item from image */
> >> } visit_info;
>
> > Though I'm still not sure we need a unified structure here.
>
> We can separate that stuff later.
>
> > ... (And if we do,
> > we need to do something different, a single function pointer for read or
> > write is insufficient)
>
> Enough with the type information as parameter.
No, I don't think so, not without going with a varargs scheme, and I
*really* don't want to do that. 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.
> But we might have
> individual entries later for speed reasons.
>
> Do you want to have a look at current state? Its already
> freezing/thawing nested and self-refed Arrays.
Yeah, I'd like to have a look. I definitely want to get the API nailed
down.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
