Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!apple!keith
From: keith@Apple.COM (Keith Rollin)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MacApp under Sys 7
Message-ID: <53566@apple.Apple.COM>
Date: 2 Jun 91 22:56:46 GMT
References: <1991Jun1.225934.7267@ux1.cso.uiuc.edu>
Organization: Apple Computer Inc., Cupertino, CA
Lines: 36

In article <1991Jun1.225934.7267@ux1.cso.uiuc.edu> ml27192@uxa.cso.uiuc.edu (Mark Lanett) writes:
>I want to point out a few problems people will have trying to run
>MPW 3.2, and MacApp in particular, under System 7.
>
> ...
>
>For MacApp there are other problems. Apple, in its infinite wisdom, went
>around renaming some fields in structures in the 3.2 Includes*, so the MacApp

Please don't blow this out of proportion. _A_ field was changed in
_a_ structure. This wasn't a case of randomly changing fields names
all over the header files.

>source won't compile. You must use the 3.1 Includes. It doesn't appear
>to link with the 3.2 libraries, either, so I'm using the 3.1 stuff there
>also. This is a problem because the MABuildTool will set up the link
>with the 3.2 libraries if it detects the 3.2 shell (do you get the feeling
>that someone at Apple wasn't testing things here?).

Apple _was_ testing. First of all, Technote #280, released over 8
months ago, documents the changes necessary to compile MacApp 2.0.1
under MPW 3.2. Secondly, there is a line in the MacApp Startup file
that you can comment out that will allow MacApp to be compiled under
MPW 3.2:

# for compatibility with MPW 3.1 ( the currently released product )
# for MPW 3.2 or later remove or comment out the following line
SET MABuildDefaults "{MABuildDefaults} -d qMPW31=TRUE"


-- 
------------------------------------------------------------------------------
Keith Rollin  ---  Apple Computer, Inc. 
INTERNET: keith@apple.com
    UUCP: {decwrl, hoptoad, nsc, sun, amdahl}!apple!keith
"But where the senses fail us, reason must step in."  - Galileo