Re: A83: Unsquish

To: assembly-83@lists.ticalc.org
Subject: Re: A83: Unsquish
From: Scott Dial <homosapian@geocities.com>
Date: Fri, 05 Mar 1999 12:58:32 -0500
Delivered-To: assembly-83-outgoing@towerguard.unix.edu.sollentuna.se
Delivered-To: assembly-83@lists.ticalc.org
Organization: ByMe Inc. Technologies
References: <ea179a81.36df2701@aol.com>
Reply-To: assembly-83@lists.ticalc.org


It isn't that difficult... but it isn't worth the effort since there is
already a disassembler. 

AtmaZ@aol.com wrote:
> 
> In a message dated 3/3/99 8:11:32 AM Mountain Standard Time, timagic@yahoo.com
> writes:
> 
> >   It wouldn't be that hard to make a decompiler in Visual Basic.  Just
> >  have to know how the 83p file is stored first.  I might fiddle with it
> >  a little and see what I can do.
> 
> Working on that right now, actually...I think I know how to read the 83P, but
> the only problem is trying to translate the hex code (let's say 3E1FD310C9)
> into readable assembly mnemonics.   I know you could use a look-up table, but
> the problem is is that Z80 opcodes don't follow the tried-and-true rule of
> "instruction pair value pair".  Some use four pairs to describe an
> instruction, some only use one... <sigh>  Right now I'm having hell trying to
> think of a way to differienate between an instruction with one opcode and one
> with four.
> 
> --David

-- 
Scott "_Wrath_" Dial
homosapian@geocities.com
ICQ#3608935
http://www.geocities.com/~homosapian/

References:

Re: A83: Unsquish

From: AtmaZ@aol.com