Path: utzoo!utgpu!watmath!julian!uwovax!2014_5001
From: 2014_5001@uwovax.uwo.ca
Newsgroups: comp.lang.c
Subject: Re: Recommend a C compiler?
Message-ID: <3608@uwovax.uwo.ca>
Date: 21 Aug 89 14:56:59 GMT
References: <660054@hpclwjm.HP.COM> <3642@ohstpy.mps.ohio-state.edu> <2420@hp-sdd.hp.com>
Lines: 41

In article <2420@hp-sdd.hp.com>, craigb@hp-sdd.hp.com (Craig Bosworth) writes:
> Followup To: 
> Distribution: 
> Organization: Hewlett Packard, San Diego
> Keywords: 
> 
> Contrary to a previous poster's assertion, there is a way to use external 
> libraries with Turbo C (2.0, anyway).  You need to create a project file
> (which lists module dependencies, etc.), including the library name.   
> 
> A project file might contain (from Turbo C User's Guide, p. 36):
> 
> 		MYMAIN (MYFUNCS.H, SPECIAL.OBJ)
> 		MYFUNCS (MYFUNCS.H, OTHER.LIB)
> 		SPECIAL.OBJ
> 		OTHER.LIB
> 
> This (among other things) causes OTHER.LIB to be linked in.  For a discussion
> of project files see the User's Guide, pp. 29-36.
> 
> I use Turbo for its speed, debugger, and integrated environment.  Microsoft
> offers these features, but to get them you have to use QuickC, then (if
> necessary) switch to the fullblown command line version for production code.
> I am concerned, however about Turbo's reputation for being a little buggy. It
> hasn't gotten me yet, but if it does it of course will be at the worst possible
> time...
> 
> BOS
> 
> Direct "my compiler's better than your compiler" posts to
> alt.religion.computers, please.

Sorry if I wasn't very clear.  I did mean that you can use the project
facility.  I LOVE the project facility.  I find that it is no great problem to
specify a project file.

----
Alex Pruss
Department of Applied Mathematics, Astronomy,
Mathematics, or Physics                     University of Western Ontario 
pruss@uwovax.uwo.ca         pruss@uwovax.BITNET          A5001@nve.uwo.ca