Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!wuarchive!decwrl!ucbvax!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: How to Argue Technical Points (was Re: Tail patches)
Message-ID: <9186@hoptoad.uucp>
Date: 5 Dec 89 02:43:28 GMT
References: <2744@dogie.macc.wisc.edu>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 24

In article <2744@dogie.macc.wisc.edu> yahnke@vms.macc.wisc.edu (Ross Yahnke,
MACC) writes:
>Apple documents all traps that may move memory, as an aid to promote
>safe programming practices. Would it make any sense or be any help 
>if Apple were to do a similar list? How about a tech note that
>documents which traps are patched, and maybe for what reason, so
>as to guide those who will inevitably go and patch things in spite
>of Apple's admonitions?
>
>That would seem to me to be an 'official' way for Apple to say, 
>"Don't tail patch, but if you do - here's what to watch out for..."

Then they would be forever limited to only those come-from patches that
are now in place.  The whole point of this mechanism is the ability to
fix bugs that are accidentally introduced into the ROMs.  I'm sure
Apple would love to commit to having bugs only in certain parts of the
system, but it's not possible.
-- 
Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com

FROM THE FOOL FILE:
"I wouldn't work for Dukakis if my life depended on it.  I've worked for
 Greeks and I know just how filthy and stinking they can be."
    -- Caller, KGO-AM, 8 Nov 88