Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MacsBug dcmd's in ThinkC
Message-ID: <10246@hoptoad.uucp>
Date: 14 Feb 90 21:23:40 GMT
References: <6650@internal.Apple.COM> <2933@draken.nada.kth.se>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 19

In article <2933@draken.nada.kth.se> d88-jwa@nada.kth.se (Jon W{tte) writes:
>THINK C is better than MPW in handling standalone code reources...

I *definitely* don't agree with that.  Building any software that has
more than one code resource is a real pain in THINK C; you've got to
ResEdit the resources from one file to the next by hand, a very tedious
operation.  You also have to open and close multiple projects and give
several build commands by hand.  In MPW, you just write a makefile and
combine all the pieces with Rez.  I don't even think that THINK C has
any noticeable performance advantage when building code resources; its
linker isn't exactly blazing fast itself; and MPW requires far less
programmer effort per build, which is what really counts.  THINK C's
advantages seem to be in the area of quick application
prelink-and-test, and not much else.
-- 
Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com

"Those who restrain desire, do so because theirs is weak enough to be
 restrained..." - Blake, "The Marriage of Heaven and Hell"