🚀 go-pugleaf

In article <560@internal.Apple.COM> lsr@Apple.COM (Larry Rosenstein) writes:
 >In article <00hRU1eOR21010a14Eo@amdahl.uts.amdahl.com> kucharsk@amdahl.uts.amdahl.com (William Kucharski) writes:
 >
 >>producing 100% legal Macintosh code.  Basically, I've found that if you
 >>try as much as possible to play by the rules of the games (read: treat
 >>Inside Macintosh as a bible) the rules won't be changed from under you (or at
 >>least _too_ badly :-) ).
 >
 >In my experience, it also depends on how cautious the developer is.  It is
 >virtually impossible for us to write down all the things you shouldn't do.
 >

 (Example concerning styled TextEdit deleted)


Oh, by no stretch of the imagination did I mean to be flaming Inside Macintosh
(seriously!).  I agree that the majority of programs that "blow up" when moving
to a new Macintosh design or new System do so because of the programmer's not
thinking about the consequences of his/her actions.  I've just found that it's
a lot easier to think through such consequences when you _do_ take Inside Mac
as gospel.  While I agree that you can't possibly document everything a programmer
_shouldn't_ do, if you follow Inside Mac you will have a far easier time than if you
take a "Apple be damned" attitude towards things.

Sorry for any confusion my earlier posting may have caused...

-- 
					William Kucharski

ARPA: kucharsk@uts.amdahl.com
UUCP: ...!{ames,decwrl,sun,uunet}!amdahl!kucharsk

Disclaimer:  The opinions expressed above are my own, and may not agree with
	     those of any other sentient being, not to mention those of my 
	     employer.  So there.