Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!intercon!amanda@intercon.UUCP From: amanda@intercon.UUCP (Amanda Walker) Newsgroups: comp.sys.mac.programmer Subject: Re: Re: System 7.0 Q & A Message-ID: <18-May-89.104411@192.41.214.2> Date: 18 May 89 14:34:41 GMT References: <811@key.COM> <30353@apple.Apple.COM> <4666@okstate.UUCP> <1787@internal.Apple.COM> <7266@hoptoad.uucp> <13472@dartvax.Dartmouth.EDU> <7321@hoptoad.uucp> <30935@apple.Apple.COM> Sender: news@intercon.UUCP Reply-To: amanda@intercon.UUCP (Amanda Walker) Organization: InterCon Systems Corporation, Sterling, VA Lines: 19 In article <811@key.COM>, perry@key.COM (Peter Kiehtreiber) writes: > After watching this line of discussion for a while, I can't keep still > any longer. Could somebody please explain to me WHY all the applications > in a Mac with PMMU have to share their low-memory globals? I think Phil's point was that a number of applications use low memory globals to monitor real-time status (such as the tick count), and it gets pretty uneconomical to have to update this all the time. That's why all of the compatibility guidelines for a while have said "USE TRAPS" in big letters. It's a lot simpler for everyone to only retrieve the status when it's asked for, rather than trying to continually update the process image... -- Amanda Walker InterCon Systems Corporation -- "You don't have to take my word for it--I'll convince you!" --Gurshuran Sidhu