Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!tecot
From: tecot@Apple.COM (Ed Tecot)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MacroMaker does strange things to the system...
Message-ID: <32327@apple.Apple.COM>
Date: 9 Jun 89 07:53:04 GMT
References: <789@tekno.chalmers.se> <7459@hoptoad.uucp>
Organization: Apple Computer Inc, Cupertino, CA
Lines: 19

In article <7459@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes:
>In article <789@tekno.chalmers.se> d83_sven_a@tekno.chalmers.se
>(Sven (Sciz) Axelsson) writes:
>>QUESTION: Why is it that Apples own programs always breaks all Apples own
>>programming guidelines? Other macromaking utilities (such as QuicKeys) can
>>manage without disrupting the journaling mechanism.
>
>I sympathize.  The reason is that they think they can get away with
>it.  It's a well-known fact that Apple's own software is often the
>least compatible with system software revisions (and the same goes, I
>understand, for high-ranking Apple alumni like Andy Hertzfeld), and it
>is a problem.  But in this case, it's not really a serious one.

And I'd argue that it's not one at all...  Journaling was built with macros
in mind (and guided tours, but I digress).  It's foolish to assume that you
are the only one using a given service in the Macintosh.  Always be prepared
to share.

						_emt