Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!ginosko!xanth!mcnc!ncsuvx!ecemwl!jnh
From: jnh@ecemwl.ncsu.edu (Joseph N. Hall)
Newsgroups: comp.sys.mac.programmer
Subject: Re: stdin and stdout in MPW C 3.0
Keywords: stdin, stdout, MPW 3.0
Message-ID: <4170@ncsuvx.ncsu.edu>
Date: 12 Oct 89 18:44:25 GMT
References: <501@dftsrv.gsfc.nasa.gov> <16055@dartvax.Dartmouth.EDU>
Sender: news@ncsuvx.ncsu.edu
Reply-To: jnh@ecemwl.UUCP (Joseph N. Hall)
Organization: North Carolina State University
Lines: 22

In article <16055@dartvax.Dartmouth.EDU> earleh@eleazar.dartmouth.edu (Earle R. Horton) writes:
>The arrangement of the MPW runtime libraries is not optimum for the
>creation of Macintosh applications.  I believe that that is what you
>wanted to hear.  Unfortunately, there is not enough documentation
>supplied so that you know enough to rearrange things, without spending
>a lot of wasted time hacking around in object dumps.

There is relatively little (except the inconvenience of splitting out a
bunch of inline assembly) that could keep you from reworking the THINK C
runtime libraries for use with MPW.  Once you've sprung for MPW, you might
as well go ahead and buy THINK C anyway, since it is generally possible
to develop in THINK C (i.e., do most of your interim compiles), and do
final compiles and the other MPW-related goodies (like archiving your sources
periodically with Projector) with MPW.  The cost is < $200 more, and that
gets you a compiling thoroughbred built for speed (but not necessarily for
flexibility).


v   v sssss|| joseph hall                      || 4116 Brewster Drive
 v v s   s || jnh@ecemwl.ncsu.edu (Internet)   || Raleigh, NC  27606
  v   sss  || SP Software/CAD Tool Developer, Mac Hacker and Keyboardist
-----------|| Disclaimer: NCSU may not share my views, but is welcome to.