Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!usc!apple!tecot
From: tecot@Apple.COM (Ed Tecot)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Tail patches
Message-ID: <36880@apple.Apple.COM>
Date: 30 Nov 89 06:45:10 GMT
References: <5249@internal.Apple.COM> <17090@dartvax.Dartmouth.EDU>
Organization: Apple Computer Inc, Cupertino, CA
Lines: 29

In article <17090@dartvax.Dartmouth.EDU> erics@eleazar.dartmouth.edu (Eric Schlegel) writes:
>In article <5249@internal.Apple.COM> chewy@apple.com (Paul Snively) writes:
>>In article <1989Nov16.043300.8959@eng.umd.edu> russotto@eng.umd.edu 
>>(Matthew T. Russotto) writes:
>>> In article <5212@internal.Apple.COM> chewy@apple.com (Paul Snively) writes:
>>> >
>>> >And I'd be interested in any examples of "something that we have 
>>> >decided to break," let alone something that we have decided to break 
>>> >and then not fix.

Okay boys and girls, call off the wolves.  Keep in mind that he's relatively
new to the net.  Please treat him a little nicer lest he run with his tail
between his legs and never return.  I'm sure none of us want to see that
happen.  Perhaps a few of us can even identify with it (right, Byron?)
What Paul was trying to point out was that we don't intentionally break
things.  When changes need to be made, we attempt to do make it as painless
as possible.  See Tech note 227 "Toolbox Karma" for even more handwaving.

>Resource Header Application Bytes were 128 bytes of data at the beginning
>of a resource file that supposedly were available for application use.
>This is documented on pp. 128-9 of IM, volume 1. Tech Note 62, from Jan. 1986,
>states that applications should no longer use these bytes as they're 
>reserved for future use by the Resource Manager.

No one seemed to be using them anyway.  We decided to reserve them so that
we might be able to make improvements to the Resource Manager in the future.
Applications are still free to use the data fork or create their own resource.

						_emt