Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!ucbvax!PAVEPAWS.BERKELEY.EDU!dillon
From: dillon@PAVEPAWS.BERKELEY.EDU (Matt Dillon)
Newsgroups: net.micro.amiga
Subject: Re: How to prevent system death from errors in user code?
Message-ID: <8605310909.AA00952@pavepaws>
Date: Sat, 31-May-86 05:09:27 EDT
Article-I.D.: pavepaws.8605310909.AA00952
Posted: Sat May 31 05:09:27 1986
Date-Received: Sun, 1-Jun-86 10:16:19 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of California at Berkeley
Lines: 14


	Unfortunetly, since the Amiga does not have an MMU, an error in
a user program is more likely to overwrite vital system storage (or other
user programs).  Dat's za vey it goes.  The only way to improve on
Developer's System Crash (DSC Syndrome, not to be confused with DHC 
Syndrome 'Developer's Head Crash'), is to run-time check as much as 
your willing to code in to attempt to catch error's before they do 
something destructive.

					-Matt

"juz 'was a little thung, Ah called ClearMenuStrip with the Menu
structure instead of the Window structure, and the System said
bye bye"