Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 UW 5/3/83; site uw-beaver
Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!houxm!vax135!cornell!uw-beaver!info-mac
From: info-mac@uw-beaver (info-mac)
Newsgroups: fa.info-mac
Subject: Re:  Macintosh language benchmarks
Message-ID: <2235@uw-beaver>
Date: Fri, 16-Nov-84 02:49:58 EST
Article-I.D.: uw-beave.2235
Posted: Fri Nov 16 02:49:58 1984
Date-Received: Sat, 17-Nov-84 03:42:38 EST
Sender: yenbut@uw-beave
Organization: U of Washington Computer Science
Lines: 26

From: olson@harvard.ARPA (Eric Olson)
I think "notoriously awful" is a little harsh as a description for
Whitesmith's C available from SoftWorks.  Although the code may
be somewhat bloated (I haven't checked this thoroughly yet), the
developement system is extremely complete, including C compiler
and Apple's ASM, LINK, EDIT, and RMAKER.  Since it has a resource
compiler, it is at leat possible to create a Mac-style application
in correct Mac STYLE (i.e., without any resources in-line in the
code).  I consider this VERY important.  This C runs on a 128K Mac
with (preferably) 2 drives (but of course would work with one).  The
turn-around time for Compile/Link/Rmaker is about 5-10 minutes.

My point is this:  It is a REAL system that can generate REAL Mac
Applications on 1 (count 'em -- 1) Mac and nothing else.

In regards to the linker:  It's true, there is no function extractor
(indeed, no librarian at all), but they supply the source for all
but the core C libraries, so you can take what you need and generate
your own libraries.  In fact, just by splitting up the libraries
into smaller chunks (right now they are OS, Toolbox, and Quickdraw,
C .asm sources and C .c sources) a lot of this problem goes away.

So let's be fair:  it works, it's not too slow, and its STANDALONE!
In my book, that's pretty darn good in MacIntosh world.

-Eric