Re: [Oopic-compiler-devel] Reverse-engineering the OOpicMK compiler--preliminary

[Neil D. <nd...@us...>]

D. Daniel McGlothin wrote:
> OK, ok, I did it.
> 
> 
> Attached is a (partial) disassembly of the bytecode stream and other files:
>     BasicSyntax.osc -- human readable byte-code listing
>     BASICSYNTAX.oex -- the HEX file of the above
>     BASICSYNTAX.Omp -- human readable object map
>     OOpic byte-codes generated by the OOpicMK compiler.xlr -- Microsoft
> Works spreadsheet disassembly notes
>     OOpic byte-codes generated by the OOpicMK compiler.xlr -- Microsoft
> Excel 95 version of the same.
>     OOpicMK_commandline.txt -- notes about the OOpicMK.exe operation
> 
> 
> If the spreadsheets are a problem, I'll render the stuff as a text file.
> 
> Please take a look at the OEX file in a hex editor and see if the ASCII
> codes of the bytes match that shown in the second 'column' of the OSC
> (assembler listing).  I suspect it does.

Excellent work!!!  I have written a little Perl utility to read in a .Ops
opcode file, and generate a .hex file containing the opcode bytes nicely
tabulated in hex format.  To use it, just type:

  perl ops2hex.pl BASICSYNTAX.Ops  (or whatever file you're converting)

and a corresponding .hex file will be generated.

I have checked, and the generated hex (from the op-codes file) matches the
OEX file perfectly.

I've attached the perl utility and the .hex file,

Neil
-- 
Neil Durant
<nd...@us...>