Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: DDPWrite Problem found
Message-ID: <7869@hoptoad.uucp>
Date: 6 Jul 89 05:29:34 GMT
References: <5920@hubcap.clemson.edu>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 18

In article <5920@hubcap.clemson.edu> mikeoro@hubcap.clemson.edu (Michael
K O'Rourke) writes:
>Thanks to those who responded to my earlier problem with a DDPWrite call
>causing an error code of -95. It turned out I was trying to access data in 
>a nil pointer earlier in the program and this ended up writing to some 
>nasty area of memory, which caused the DDPWrite error.  

Gosh, I wonder why we nasty ol' developers keep begging Apple for a
memory protected OS.  It must be that we're just jerks -- after all, we
disagree with stated Apple policy and plans, and only a real asshole
would do that.  There couldn't possibly be a good reason we consider
memory protection important, could there?
-- 
Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com
Postal: 424 Tehama, SF CA 94103; Phone: (415) 495-2934

"Please help support the moratorium on meaningless quotes in .signatures."
  -- Doug Asherman on rec.music.cd