Xref: utzoo comp.lang.c:7598 comp.sys.ibm.pc:12473
Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!agate!ig!uwmcsd1!tut.cis.ohio-state.edu!ut-sally!nather
From: nather@ut-sally.UUCP (Ed Nather)
Newsgroups: comp.lang.c,comp.sys.ibm.pc
Subject: Re: TurboC: Stupid Linker ?
Message-ID: <10488@ut-sally.UUCP>
Date: 26 Feb 88 17:50:45 GMT
References: <2622@i.cc.purdue.edu> <307@bernina.UUCP>
Organization: U. Texas CS Dept., Austin, Texas
Lines: 14

In article <307@bernina.UUCP>, zu@ethz.UUCP (Urs Zurbuchen) writes:
> 
> I read in the manual to Data&Windows that the Turbo-C linker tlink does NOT
> report unresolved externals. Can anybody confirm? Or proof the contrary
> (which would be much better for Borland).
> 

My copy of Turbo C's linker reports them.  Sometimes several pages of them
when I've forgotten an "#include" statement ...

-- 
Ed Nather
Astronomy Dept, U of Texas @ Austin
{allegra,ihnp4}!{noao,ut-sally}!utastro!nather
nather@astro.AS.UTEXAS.EDU