Path: utzoo!utgpu!attcan!uunet!sco!seanf
From: seanf@sco.COM (Sean Fagan)
Newsgroups: comp.lang.c
Subject: Re: MSC multiple-definition bug or feature?
Keywords: Strange MSC linker behavior
Message-ID: <1563@scolex>
Date: 22 Oct 88 22:19:29 GMT
References: <6215@bunny.UUCP> <1099@dutinfd.UUCP>
Reply-To: seanf@sco.COM (Sean Fagan)
Organization: The Santa Cruz Operation, Inc.
Lines: 25

In article <1099@dutinfd.UUCP> oosten@dutinfd.UUCP (Gertjan van Oosten) writes:
|In article <6215@bunny.UUCP>, rhb6@bunny.UUCP (Robert H. Barkan) writes:
|In one C file, I had the following (external) declaration: 
|static int x; 
|In another C file, I had: 
|extern int x; 
|
|Compilation and linkage produced no "Unresolved external" message!!!!! 
|How nice of Microsoft.... 
|I also tried this on four other machines. Here come the results, fasten 
|seatbelts and refrain from smoking: 
[says that only 4.3BSD works correctly.]

Running XENIX, for the '386, Microsoft C Compiler (also '386), the linker
complains bitterly.
Also, lint ends up (quite nicely, I think) complaining that x is used but
never defined in t1.c, and that x is defined but never used in t2.c (which
is, of course, correct).

So this means that Xenix is as good as 4.3 BSD?  Glad *somebody* realized it
8-).
-- 
Sean Eric Fagan  | "ld runs like a turtle out of antartica"
seanf@sco.UUCP   |     Steven Ryan (smryan@garth.UUCP)
(408) 458-1422   | Any opinions expressed are my own, not my employers'.