Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!munnari.oz.au!comp.vuw.ac.nz!cavebbs!frank
From: frank@cavebbs.gen.nz (Frank van der Hulst)
Newsgroups: comp.lang.c
Subject: Re: Turbo C and Clipper .OBJ files
Message-ID: <1991May31.074059.9126@cavebbs.gen.nz>
Date: 31 May 91 07:40:59 GMT
Article-I.D.: cavebbs.1991May31.074059.9126
References: <261.28449770@weyr.FIDONET.ORG>
Organization: The Cave MegaBBS, Public Access Usenet, Wellington, NZ
Lines: 14

In article <261.28449770@weyr.FIDONET.ORG> rensberry@p4.f22.n140.z1.FIDONET.ORG (Clark Rensberry) writes:
>Hi,
>
>I've got Turbo C 2.0 and I program extensively in Clipper.  I built a simple graphics program in Turbo C and then assumed (what a mistake) that I could link it's OBJ file in with the rest of my compiled Clipper Code and link it with PLink86.  I also tried the MS-DOS linker as well.  No luck - There were library problems and routines being called that didn't exist (so said PLink86 in Verbose mode).
I think your problem is that Turbo C generates calls to functions available in
ints libraries -- things like PCMP@ (for pointer comparison, if you use e.g.
if (ptr == NULL) ), which are not available in Clipper's library. Try linking
CL.LIB with your stuff too.


-- 

Take a walk on the wild side, and I don't mean the Milford Track.
Kayaking: The art of appearing to want to go where your boat is taking you.