Simon --
> I think that's exactly what needs work, and one of the things Gregor
> is looking at. Here's how it goes.
>
> Before 0.0.2 is released, we need to pass tests on Sparc,
Someone else has to tinker with this this... (no Sparc here)
> which means we need to stop dereferencing NVs on bad alignments,
(no Sparc here)
> which means we need to move NVs into the constant table,
I'm prepared to do this very soon (perhaps tomorrow if my patch from
earlier today is Good To Go -- let me know).
> which means we need to make the constant table grok different types,
I'm prepared to do this very soon (see above).
> which means we need to rewrite the bytecode structure and code.
I'm prepared to do this very soon (see above)l.
> I'll post something when I'm not completely and utterly shattered about how I
> want us to go about that, including how the interpreter's interface to the
> "pack file" - the bytecode with all its segments - will change while we're at
> it to allow multiple packs in the same file, something very useful if we want
> to do, say, subroutines.
I'd like to see the changes for 0.0.2 be just the bare minimum for the
const_table containing NVs + SVs. I know a bunch of us have been
thinking about the file format stuff and we'll probably want to have
another thread about it before adding more stuff (IMHO).
Is there hope that 0.0.2 could be out by the end of the week if I get
the tasks assiged to me done RSN?
Regards,
-- Gregor
_____________________________________________________________________
/ perl -e 'srand(-2091643526); print chr rand 90 for (0..4)' \
Gregor N. Purdy [EMAIL PROTECTED]
Focus Research, Inc. http://www.focusresearch.com/
8080 Beckett Center Drive #203 513-860-3570 vox
West Chester, OH 45069 513-860-3579 fax
\_____________________________________________________________________/