Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!eru!luth!sunic!dkuug!freja.diku.dk!skinfaxe.diku.dk!jensting
From: jensting@skinfaxe.diku.dk (Jens Tingleff)
Newsgroups: comp.lang.c
Subject: Re: OK, so why _does_ ld resolve text against data?
Message-ID: <1990Aug24.065123.13481@diku.dk>
Date: 24 Aug 90 06:51:23 GMT
References: <37909@ucbvax.BERKELEY.EDU> <930@eplunix.UUCP> <3605@goanna.cs.rmit.oz.au> <13657@smoke.BRL.MIL>
Sender: news@diku.dk (The Netnews System)
Organization: Department Of Computer Science, University Of Copenhagen
Lines: 19


As someone points out, this is *not* a problem in the linker, but a problem
with the language. Check, for instance, Modula-2, where the external names are
*only* brought in together with the (object) module from which they should
be extracted at link time. The ``FROM foo IMPORT blahh'' method solves
the problem, since ``foo'' only contains one visible ``blahh'', and the 
linker doesn't care how many ``blahh''s are floting around out there. 

[yes, you can redefine the PROCEDUREs used by library modules. If such a 
need arises, the relevant PROCEDURE could be a procedure variable which is
assigned a non-default value by the users code]

Back to C...

	Jens
Jens Tingleff MSc EE, Institute of Computer Science, Copenhagen University
Snail mail: DIKU Universitetsparken 1 DK2100 KBH O
"It never runs around here; it just comes crashing down"
	apologies to  Dire Straits