Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!news.cs.indiana.edu!news.nd.edu!mentor.cc.purdue.edu!descartes.math.purdue.edu!wilker
From: wilker@descartes.math.purdue.edu (Clarence Wilkerson)
Newsgroups: comp.sys.amiga.emulations
Subject: Re: Emulator Mechanics (sorry long post)
Message-ID: <7578@mentor.cc.purdue.edu>
Date: 10 Mar 91 17:26:27 GMT
References: <1323@macuni.mqcc.mq.oz> <4992@mindlink.UUCP> <1991Mar6.004247.8964@cpsc.ucalgary.ca> <2406@taurus.BITNET>
Sender: news@mentor.cc.purdue.edu
Reply-To: wilker@descartes.math.purdue.edu (Clarence Wilkerson)
Lines: 9

On the subject of self modifying code, I can think of one place on the
80X8Y where it's tempting:
   INT   X
where X is a byte code for the interrupt number. Since there is no other
mechanism to
call a software interrupt, and any C-library  for the PC supports calls like
Intr( number, args), I suspect that self-modifying code is used.  On the
other hand, a
case statement with 256 cases could be used .....