Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!dogie.macc.wisc.edu!vms.macc.wisc.edu
From: yahnke@vms.macc.wisc.edu (Ross Yahnke, MACC)
Newsgroups: comp.sys.mac.programmer
Subject: Re: How to Argue Technical Points (was Re: Tail patches)
Message-ID: <2744@dogie.macc.wisc.edu>
Date: 30 Nov 89 17:43:51 GMT
Sender: news@dogie.macc.wisc.edu
Organization: University of Wisconsin Academic Computing Center
Lines: 12

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

>>>      Internet: yahnke@macc.wisc.edu        <<<
>>>   Mille voix chuchottent <<c'est vrai>>    <<<