Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!osu-eddie!mdf
From: mdf@osu-eddie.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: Clipper/MS C Linking
Message-ID: <2789@osu-eddie.UUCP>
Date: Sun, 28-Dec-86 20:46:54 EST
Article-I.D.: osu-eddi.2789
Posted: Sun Dec 28 20:46:54 1986
Date-Received: Mon, 29-Dec-86 05:37:05 EST
References: <627@tetra.UUCP>
Reply-To: mdf@osu-eddie.UUCP (Mark D. Freeman)
Organization: InfoSolv Corporation; Columbus, OH. (guest Ohio State U.)
Lines: 22
Summary: Can't be done

In <627@tetra.UUCP> swatson@tetra.UUCP (Steven B. Watson) writes:
>Has anyone successfully used the Clipper compiler and plink86 to link
>clipper object files with object files produced by MS C 4.0?

It is impossible.  Those silly people at Nantucket used symbol names
that conflict with those in the MS C libraries.  The wrote Clipper in
Lattice C, so they didn't really notice the incompatibility with MS C
until after release.  They don't seem very interested in fixing this.

If you need to link C modules with Clipper modules, you need to use
Lattice C.  If you need a copy, I have a copy of Lattice 3.1 I'd like to
get rid of.  I'll make you an even swap for your MS 4.0, which I need
another copy of. 

-- 
< < < < < < < < < < < < < < < < < < < <> > > > > > > > > > > > > > > > > > > >
Mark D. Freeman						    mdf@osu-eddie.uucp
InfoSolv Corporation					   mdf@Ohio-State.arpa
6099 Riverside Drive				      ...!cbosgd!osu-eddie!mdf
Dublin, OH  43017		    Guest account at The Ohio State University
(614) 761-8444
< < < < < < < < < < < < < < < < < < < <> > > > > > > > > > > > > > > > > > > >