Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!dewey.soe.berkeley.edu!oster
From: oster@dewey.soe.berkeley.edu (David Phillip Oster)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Need a review of THINK C 4.0
Message-ID: <32502@ucbvax.BERKELEY.EDU>
Date: 12 Nov 89 04:00:52 GMT
References: <1346@mrsvr.UUCP> <296@dbase.UUCP> <2127@se-sd.NCR.COM> <13734@boulder.Colorado.EDU>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster)
Distribution: na
Organization: School of Education, UC-Berkeley
Lines: 17

Sheesh, you'd think programmers would at least read the manual once in
awhile. The THINK C manual describes how to set up a group of projects
that share source files so they each use the same copy. (It involves
putting the project dependent code for the project "foo.proj" in a folder
named "(foo.proj)".) When you start work on a new project that shares
source code with an old one, use THINK C's Make Commmand, and it will
check to se if any of the source files have been modified by some other
program.  Yes, it would be nice if you could configure THINK C to auto-run
the Make when you open a new project, but since it is doing 99.99% of the
job, you should cut it a little slack.

---peevishly yours,
> The mac is a detour in the inevitable march of mediocre computers.
> drs@bnlux0.bnl.gov (David R. Stampf)
--- David Phillip Oster          -master of the ad hoc odd hack. 
Arpa: oster@dewey.soe.berkeley.edu 
Uucp: {uwvax,decvax}!ucbvax!oster%dewey.soe.berkeley.edu