Path: utzoo!attcan!uunet!ncrlnk!ncr-mpd!Chuck.Phillips From: Chuck.Phillips@FtCollins.NCR.COM (Chuck.Phillips) Newsgroups: comp.sys.amiga.tech Subject: Re: Whats wrong with self Modifying Code? Message-ID: Date: 10 Jul 90 07:20:42 GMT References: <1990Jul6.201328.24660@csmil.umich.edu> <1990Jul6.201743.24777@csmil.umich.edu> <138523@sun.Eng.Sun.COM> <1990Jul9.163607.18336@sunee.waterloo.edu> Sender: uucp@ncr-mpd.FtCollins Organization: NCR Microelectronics, Ft. Collins, CO Lines: 21 In-reply-to: mwm@raven.pa.dec.com's message of 9 Jul 90 12:45:59 GMT >>>>> On 9 Jul 90 12:45:59 GMT, mwm@raven.pa.dec.com (Mike (Real Amigas have keyboard garages) Meyer) said: Mike> All programs of this class can be done without modifying code - Mike> remember, you're creating it, not modifying it! For the first example Mike> (several thousand iterations? trivial) I'd compile to interpreted Mike> stack-machine code to run. For large applications (popi, for instance) Mike> or those where speed is more critical (your video driver), compile to Mike> an array and tell the OS you're launching a task loaded into that Mike> chunk of memory, and use that. The OS should take care of making sure Mike> the code in that memory actually gets run, and not whatever you put Mike> there last time around. This brings up an interesting point about future versions of AmigaOS and the MMU. In future versions of AmigaOS, will we need to mark this area of memory as executable to avoid MMU violations? Do we write the code into the stack or heap and then call something like LoadSeg() on it? Expiring minds want to know! -- Chuck Phillips MS440 NCR Microelectronics Chuck.Phillips%FtCollins.NCR.com Ft. Collins, CO. 80525 uunet!ncrlnk!ncr-mpd!bach!chuckp