Xref: utzoo comp.sys.mac.programmer:6299 comp.sys.mac:31926
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!violet.berkeley.edu!edmoy
From: edmoy@violet.berkeley.edu
Newsgroups: comp.sys.mac.programmer,comp.sys.mac
Subject: Re: System 8.0 Q & A
Message-ID: <24422@agate.BERKELEY.EDU>
Date: 14 May 89 20:29:56 GMT
References: <30353@apple.Apple.COM> <4666@okstate.UUCP> <1787@internal.Apple.COM> <7266@hoptoad.uucp> <8260@fluke.COM>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 33

In article <8260@fluke.COM> moriarty@tc.fluke.COM (Jeff Meyer) writes:
>As did I... but just to tie things down, does Apple's plans for their 8.0
>multi-tasking system include memory protection?

At the developer's conference this last week, there was a presentation on
the future of the Mac OS.  Though, there was no direct mention of the plans
for 8.0, they did say the following is coming:

	True pre-emptive multi-tasking.

	Protected memory.

	Improved QuickDraw engine, including graphical hardware support.

	More international support.

	A new scripting language, called AppleScript, probably based on
		HyperTalk.

Apple is moving very cautiously, as these changes will probably break many
existing programs today, which are not 32 bit clean, which write directly
to devices, which use supervisory mode instructions in the 680x0 instruction
set, or which doddle in the System heap or other applications' heap.  System
7.0 is an intermediate step, giving developers the opportunity to correct
these problems.

Edward Moy				Principal Programmer - Macintosh & Unix
Workstation Support Services		Workstation Software Support Group
University of California
Berkeley, CA  94720

edmoy@violet.Berkeley.EDU
ucbvax!violet!edmoy