Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!usc!apple!apple.com!chewy
From: chewy@apple.com (Paul Snively)
Newsgroups: comp.sys.mac.programmer
Subject: Re: How to Argue Technical Points (was Re: Tail patches)
Message-ID: <5532@internal.Apple.COM>
Date: 30 Nov 89 23:35:08 GMT
References: <2744@dogie.macc.wisc.edu>
Sender: usenet@Apple.COM
Organization: Apple Computer, Inc.
Lines: 26

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..."

It's a really great idea, but it's really not feasible because different 
Systems patch different ROMs on different CPUs differently.  That list 
would have to be revved at every System release for every CPU and every 
version of the System file.  There are also questions like: what else is 
patched if you have 32-bit QuickDraw installed?  What about having 
MultiFinder version X as opposed to not having it?  There are just too 
many variables, but thanks for the suggestion!

__________________________________________________________________________
Just because I work for Apple Computer, Inc. doesn't mean that they 
believe what I believe or vice-versa.
__________________________________________________________________________
C++ -- The language in which only friends can access your private members.
__________________________________________________________________________