Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!amdcad!ames!pasteur!ucbvax!hoptoad!tim From: tim@hoptoad.uucp (Tim Maroney) Newsgroups: comp.sys.mac.programmer Subject: Re: LSC 3.0 critique (long) Message-ID: <5476@hoptoad.uucp> Date: 28 Sep 88 20:15:33 GMT References: <2367@munnari.oz> <5453@hoptoad.uucp> <3784@phoenix.Princeton.EDU> Reply-To: tim@hoptoad.UUCP (Tim Maroney) Organization: Eclectic Software, San Francisco Lines: 20 In article <3784@phoenix.Princeton.EDU> mbkennel@phoenix.Princeton.EDU (Matthew B. Kennel) writes: >In article <5453@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes: >> If there is some way on the Mac to ensure you never write to >>other applications' memory during development, I sure would love to hear >>about it, as would the validation theorists working on SDI. > >Yes, there is a way that you never write to other application's memory: >It's called hardware memory protection. You don't think that a >multi-user computer can afford to crash whenever people dangle their >pointers? Read my lips: I said "on the Mac". I learned to program on VAXen and I don't need a memory protection 101 lecture. -- Tim Maroney, Consultant, Eclectic Software, sun!hoptoad!tim "In any religion or form of worship, followers should be allowed to think for themselves. In every religion that has a god other than Jesus Christ, adherents are not allowed to think for themselves." -- Lauren Stratford, "Satan's Underground"