Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mcnc!ncsuvx!lll-winken!uwm.edu!cs.utexas.edu!natinst!davoli
From: davoli@natinst.com (Russell Davoli)
Newsgroups: comp.sys.mac.programmer
Subject: Re: THINK C linking wish
Summary: smart linking
Keywords: smart linking
Message-ID: <16948@natinst.natinst.com>
Date: 3 Dec 90 15:29:57 GMT
References: <16796@natinst.natinst.com> <109545@convex.convex.com>
Distribution: usa
Organization: National Instruments, Austin, TX
Lines: 18

In article <109545@convex.convex.com>, ewright@convex.com (Edward V. Wright) writes:
> davoli@natinst.com (Russell Davoli) writes:
> >
> >It would be really nice if there was a way to get "smarter" linking
> >out of THINK C.  By this, I mean that the linker includes only the
> >functions called in the program.  As I understand it, presently the
> >linker will link in all the functions from a file if even one of those
> >is called.  
> 
> Are you sure about that?  I know that isn't true with THINK Pascal, so
> I would be fairly surprised to find out that is with THINK C.

I don't think that the kind of linking I'm talking about is possible
with any THINK language system, but I'm no authority on their Pascal.
MPW's linker does the kind of linking I'm talking about.  That's why
I think there should be a way to optionally turn on the "smarter"
linking -- MPW's linker is SLOW, and it would be nice to have the ability
to build quickly a version for testing then do a slower build for release.