Article View: comp.sys.amiga.tech
Article #2969Re: Amiga Resource tracking & protection.
From: hamish
Date: Sat, 17 Mar 1990 00:08
Date: Sat, 17 Mar 1990 00:08
17 lines
1142 bytes
1142 bytes
I keep reading about people saying that programs should be specially written to cope with memory protection. Memory protection is a function of the OS, not the individual programs. To make it easy to run those programs that would break, then it should be able to be turned on & off, maybe on an individual basis per program. (ie the OS detecting a bounds fault & getting the data or writing the data). This would make it simple to write programs, ie nothing needs changing except how we use the MEMF_PUBLIC flag, which currently seems to be everywhere (correct me if I'm wrong, and the memory allocation routines in the OS itself. One last thing would be a memory handler routine for bad memory accesses by all thos nasty programs out there!. Hamish Marson.
Technical Details
Message-ID:
<235.260236d8@waikato.ac.nz>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!usc!elroy.jpl.nasa.gov!ames!uhccux!munnari.oz.au!kaukau.comp.vuw.ac.nz!virtue!hamishShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!usc!elroy.jpl.nasa.gov!ames!uhccux!munnari.oz.au!kaukau.comp.vuw.ac.nz!virtue!hamish From: hamish@waikato.ac.nz Newsgroups: comp.sys.amiga.tech Subject: Re: Amiga Resource tracking & protection. Message-ID: <235.260236d8@waikato.ac.nz> Date: 17 Mar 90 00:08:40 GMT Lines: 17