Xref: utzoo comp.sys.mac.programmer:5372 comp.sys.mac:29549
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ukma!husc6!bbn!apple!goldman@apple.com
From: goldman@apple.com (Phil Goldman)
Newsgroups: comp.sys.mac.programmer,comp.sys.mac
Subject: Checking for MF (was Re: Need some MF help)
Message-ID: <1179@internal.Apple.COM>
Date: 5 Apr 89 08:47:02 GMT
Sender: usenet@Apple.COM
Distribution: comp.sys.mac.programmer,comp.sys.mac
Organization: Apple Computer, Inc.
Lines: 22
References:<1562@neoucom.UUCP> <28689@ucbvax.BERKELEY.EDU>

In article <28689@ucbvax.BERKELEY.EDU> oster@dewey.soe.berkeley.edu (David 
Phillip Oster) writes:
> The standard, from Apple is "Don't even try to do this".  Most people do
> it by checking to see if the end of the system heap is close to the
> beginning of the application heap. If it is, no multifinder.

This is a very bad thing to do, and, as was mentioned in a previous 
posting, the one known legitimate reason for doing so will soon be fixed 
in SysEnvirons.

Reasons such as putting up a dialog box saying "Cannnot do...with 
MultiFinder" are very poor ones.  When MF was first released there were 
certain apps that had these same warnings for Switcher.  These dialogs 
became very embarrassing for the developers, and an annoyance for users.  
This will happen again apparently.

Doing such checks makes it very much harder to move MultiFinder 
functionality to the System or ROM.  Worse, it makes it dirtier to add new 
Mac OS functionality.

-Phil Goldman
Apple Computer