🚀 go-pugleaf

himacdon@maytag.uwaterloo.ca (Hamish Macdonald) writes:
>In addition, putting memory protection into AmigaDos is not as easy as
>you imply.   It  will   break the  vast  majority  of   existing Amiga
>programs.  All interprocess communication  in the Amiga  is done using
>shared memory techniques.  Guidelines for writing programs in a manner
>upwardly compatible with future memory protection  mechanisms have not
>existed for a long time, and have not been religiously followed in any
>case.

One Think that I have alaways wondered: is is practical implement
memory protection from one task?  Ie can the MMU be used to insure
that task X doesn't stomp on any memory that it has not allocated?
This ability would be extreemly useful for developement (even if it
required linking in special code to do resource tacking so that the
task could be shut down).   After all it's VERY annonying to have to
reboot all the time while testing a program as apposed to getting a
segmentation fault message. While this is certainly NOT an answer to
stopping guru visits under normal amigaDOS operation, it would be very
helpful for debugging.  Anyone care to comment on the practicality of
this idea?

//     Rick Golembiewski  rg20+@andrew.cmu.edu  \\
\\       #include stddisclaimer.h               //
 \\  "I never respected a man who could spell" //
  \\               -M. Twain                  //