Xref: utzoo comp.lang.c:13785 comp.sys.ibm.pc:20823
Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!iuvax!silver!creps
From: creps@silver.bacs.indiana.edu (Steve Creps)
Newsgroups: comp.lang.c,comp.sys.ibm.pc
Subject: Re: MSC v5.1 bug; variable not made public
Keywords: C,Microsoft,lib,link,TurboC
Message-ID: <2599@silver.bacs.indiana.edu>
Date: 2 Nov 88 20:00:51 GMT
References: <792@euraiv1.UUCP>
Reply-To: creps@silver.UUCP (Steve Creps)
Organization: IU CS Dept
Lines: 14

In article <792@euraiv1.UUCP> evas@euraiv1.UUCP (Eelco van Asperen) writes:
>I've just found a nice bug in MSC v5.1; if you declare an unitialized
>variable in a module that has no other publics and put that module in
>a library, the variable will _not_ be found by LINK. Here's a small

   That problem is also in MSC 4.0. I too noticed that initializing the
variable makes the problem go away. It's also possible that the bug is
actually in LIB, as the uninitialized variable still shows up in the .obj
file when I do a strings on it.

-	-	-	-	-	-	-	-	-	-
Steve Creps, Indiana University, Bloomington, home of the "Hoosiers"
	creps@silver.bacs.indiana.edu (129.79.1.6)
	{inuxc,rutgers,uunet!uiucdcs,pur-ee}!iuvax!silver!creps
	creps@iubacs.bitnet (forwarded)