siegel@endor.harvard.edu (Rich Siegel) (02/19/90)
In article <5390@okstate.UUCP> minich@a.cs.okstate.edu (MINICH ROBERT JOHN) writes: >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, The current versions of THINK C and THINK Pascal work as follows: the atomic unit in the linker is a "module" - the smallest unit of code which can be smartlinked away when building an application. When instant- running, no smart linkage is done. In both THINK C or THINK Pascal, the module is a single file, or a single entry in a project file created by converting a .O file (THINK C only). When smartlinking (building an application or code resource or DA), modules which contain no references will be removed. A module is a single C or Pascal source file, a library built with the "Build Library" command, an entry in a project document, or a .O file. Libraries built by THINK Pascal will be smartlinked down to their component files. R. ~~~~~~~~~~~~~~~ Rich Siegel Staff Software Developer Symantec Corporation, Language Products Group Internet: siegel@endor.harvard.edu UUCP: ..harvard!endor!siegel "When someone who makes four hundred and fifty dollars an hour wants to tell you something for free, it's a good idea to listen." ~~~~~~~~~~~~~~~