🚀 go-pugleaf

>>>>> 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