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.
Brian
On Mon, 2001-09-17 at 16:06, Gregor N. Purdy wrote:
> All --
>
> I'm not certain about this, but it sure doesn't look right to me.
> (note I did this after turning off fingerprint saving in the
> assembler for clarity):
>
> $ perl -e 'print "set_i I0, 4\nend\n"' | assemble.pl | od -x
> 0000000 55a1 0131 0000 0000 0000 0000 0002 0000
> 0000020 0000 0000 0004 0000 0000 0000
> 0000034
>
> * The first four bytes are the magic number
> * The next four bytes are all zero for "no fixup table here"
> * The next four bytes are all zero for "no const table here"
> * The next four bytes should be pack('l', 16) for "16 bytes
> of byte code follow (NOTE: THESE SEEM TO BE MISSING)
>
> Now, the disassembler and interpreter don't seem to care, but I
> thought the current format involved 3 or 4 segments in the
> length-payload pair format. The fourth (optional) segment according
> to the docs is a place to store the source code.
>
>
> 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
> \_____________________________________________________________________/
