Dan Sugalski <[EMAIL PROTECTED]> wrote: [ a lot of design ]
> Yes, this does bloat out the format some, but it Seems so. But anyway, can you put together a design document and check it in, so that this whole stuff isn't lost in history. Some additional random remarks and questions: * Where do these name-labels come from? * The new image format implies, that each simple item is preceeded by a tag-byte having the type of the following item. * For a dense image stream, we have to give up to use the opcode_t aligned packfile constants routines. OTOH, e.g. small integer can be coded with less bytes. * Should packfile constants use the same format? Less code duplication, less errors. * What kind of data inspection from outside do you think of? * Implementing thaw and error handling will be great fun :) I'll still add a few bits to the current scheme to be able to freeze/thaw packfile constants (Sub for now, maybe Classes). Then things can settle and await the implementation of freeze/thaw 0.2. > Dan leo
