Path: utzoo!attcan!uunet!samsung!usc!apple!apple.com!chewy
From: chewy@apple.com (Paul Snively)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Tail patches
Message-ID: <5325@internal.Apple.COM>
Date: 21 Nov 89 17:31:50 GMT
Sender: usenet@Apple.COM
Organization: Apple Computer, Inc.
Lines: 25
References:<5249@internal.Apple.COM> <17090@dartvax.Dartmouth.EDU> <5292@internal.Apple.COM> <1989Nov20.182741.2658@eng.umd.edu> <5320@internal.Apple.COM> <1989Nov21.040138.344@eng.umd.edu>

In article <1989Nov21.040138.344@eng.umd.edu> russotto@eng.umd.edu 
(Matthew T. Russotto) writes:
> In article <5320@internal.Apple.COM> chewy@apple.com (Paul Snively) 
writes:
> >Your application won't break as long as you link with up-to-date 
library 
> >code!  As for "was it hard to keep the jump," I'm not a ROM engineer, 
so I 
> >don't really know.  There were some pretty hairy changes in going from 
the 
> >old Macs to the II-family Macs.
> And just how (in 1984) was I supposed to link with up-to-date library 
code
> released in 1987?

You weren't, in 1984; you were supposed to rebuild your code every time a 
new development system was released, like everyone else who distributes 
what they write in any way.

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