Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!mp.cs.niu.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!ml27192
From: ml27192@uxa.cso.uiuc.edu (Mark Lanett)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MPW and Think
Message-ID: <1991Jun25.215324.2791@ux1.cso.uiuc.edu>
Date: 25 Jun 91 21:53:24 GMT
References: <1991Jun25.180736.28590@gn.ecn.purdue.edu>
Sender: usenet@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 17

jess@gn.ecn.purdue.edu (Jess M Holle) writes:

>After reading this, I have a pleading request for the MPW people at Apple:
>PLEASE EMPHASIZE CODE OPTIMIZATION IN FUTURE VERSIONS! If I knew that this
>was never going to happen, I'd probably switch to Think C right now. I know
>that 3.2 is done, but how about working on it for 3.3.

Gack! No Code Optimizations! That's what breaks always breaks! The version 3 C
compiler just can't deal properly with heavy register usage. And you know that
once a new bug gets introduced into MPW it's going to be there for a looooong
time.

>Jess Holle
--
//-----------------------------------------------------------------------------
Mark Lanett						mlanett@uiuc.edu
Software Tools Group, NCSA