Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!psuvax1!rutgers!okstate!minich
From: minich@a.cs.okstate.edu (MINICH ROBERT JOHN)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MPW compiler bugs
Message-ID: <5390@okstate.UUCP>
Date: 16 Feb 90 20:29:15 GMT
References: <1990Feb16.012322.19895@oracle.com>
Organization: Oklahoma State Univ., Stillwater
Lines: 27

From article <1990Feb16.012322.19895@oracle.com>, by gstein@oracle.com:
> Hmm...
> 
> I had thought that Think C works on a file by file basis.  If you
> include a routine from a file, the WHOLE file is pulled in.  Note,
> though, that this doesn't count for projects/libraries: in these it
> picks the file out of the project.  As for the ANSI library, Think has
> split up the source into a bunch of tiny files.  Since you use one
> routine, you get one (little) file.  I know that using "Run..."
> doesn't do any dead code analysis and you pick up whole libraries/
> projects (e.g. MacTraps), but building is different.
> 
> Maybe I'm brain dead and they've fixed this.  Unfortunately, I have to
> wait until I get home to check cuz we don't use Think C here at work :-(
> Greg Stein

  I am not sure about THINK C, but I know the way THINK Pascal works, it
does include entire files when you're debugging, but when you "Build..."
and check "Smart Linking", it does go routine by routine. I've had a 
couple occasions where I picked out a couple routines out of each of many
seperate files. The total of all the files wouldn't fit into one segment
unless I did the Build.. with Smart Linking. Oc course, I went and deleted
the majority of the source, which I didn't happen to be using, so I could
debug the darn thing!

Robert Minich
minich@a.cs.okstate.edu