Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!apple!voder!pyramid!infmx!greggy
From: greggy@infmx.UUCP (greg yachuk)
Newsgroups: comp.sys.ibm.pc
Subject: Re: MSC multiple-definition bug or feature?
Keywords: Strange MSC linker behavior
Message-ID: <553@infmx.UUCP>
Date: 20 Oct 88 19:09:07 GMT
References: <6215@bunny.UUCP>
Reply-To: greggy@infmx.UUCP (greg yachuk)
Organization: Informix, Menlo Park, Ca. U.S.A.
Lines: 19

In article <6215@bunny.UUCP> rhb6@bunny.UUCP (Robert H. Barkan) writes:
>
>In MSC 5.x, compile the following 2 files, then link x1.obj and y1.obj.
>The linker should complain because "int x" is multiply defined:
	[ code deleted ]

I just got my 5.1 updgrade yesterday, so I tried your example.
Version 3.65 (which comes with 5.1) doesn't complain about any
of the combinations that you mention.  I tried the 3.61 linker
(from 5.0), and still didn't get any complaints.  Of course, for
the final combo (int x and int *x), the executable was incorrect
from both linkers.

The point is: howcum you linker complained and mine was silent?

>Bob Barkan				GTE Laboratories

Greg Yachuk		Informix Software Inc., Menlo Park, CA	(415) 322-4100
{uunet,pyramid}!infmx!greggy		why yes, I DID choose that login myself