Brian --
> As near as I can tell, its always been just the bytecode following
> without a length specifier. I was going to play with it, but since
> we're still deciding on the file format, I thought I'd leave it alone.
Yeah, I just read bytecode.c again and sure enough that's it. My code
is working now. It doesn't match the current docs, though. The current
docs say there can be another segment after the bytecode segment that
contains source code.
I'm going to check in some more Perl code today for mucking with
Parrot::PackFiles with their magic numbers, Parrot::FixupTables,
Parrot::ConstTables (containing Parrot::Constants), and byte code.
My hope is that the assembler and disassembler can use these for their
reading and writing so that when the format changes we just change the
library. I'm not going to muck with the assembler and disassembler
myself just yet (although if nobody else volunteers soon I may give
it a go).
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
\_____________________________________________________________________/
