Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!think!ames!ucbcad!zen!cory.Berkeley.EDU!schung
From: schung@cory.Berkeley.EDU (Stephen the Greatest)
Newsgroups: comp.lang.c
Subject: Re: Types
Message-ID: <3384@zen.berkeley.edu>
Date: Mon, 24-Aug-87 12:31:40 EDT
Article-I.D.: zen.3384
Posted: Mon Aug 24 12:31:40 1987
Date-Received: Tue, 25-Aug-87 03:57:43 EDT
References: <7264@brl-adm.ARPA> <734@sdchema.sdchem.UUCP>
Sender: news@zen.berkeley.edu
Reply-To: schung@cory.Berkeley.EDU.UUCP (Stephen the Greatest)
Organization: University of California, Berkeley
Lines: 15

>All that needs to done is to have each library routine avaliable in each
>combo of models, and a smart linker which can use them.
>-- 
>John Plocher uwvax!geowhiz!uwspan!plocher  plocher%uwspan.UUCP@uwvax.CS.WISC.EDU


	And now something completely different...

	What about an object file format that does not distinguish between
	near/far pointer usage?  Have the (real smart) linker generate the
	right code from these object files.  This will put more work to the
	linker, but make sure that only one version of each library routine
	must be written.

					- Stephen