Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!dixie.com!nanovx!msa3b!kevin
From: kevin@msa3b.UUCP (Kevin P. Kleinfelter)
Newsgroups: comp.databases
Subject: Re: CLIPPER 5.0 BC++ compatibility
Message-ID: <1588@msa3b.UUCP>
Date: 5 Apr 91 17:25:27 GMT
References: <16105.27fafba0@levels.sait.edu.au>
Organization: Dun and Bradstreet Software, Inc., Atlanta, GA
Lines: 24

marwk@levels.sait.edu.au writes:

[...]
>I want to use BORLAND C++ 2.0 in conjunction with CLIPPER.
>This precludes the use of floating point arithmetic.  For that I have to
>use Microslop C - why is it necessary for me to purchase another package when
>for all other puposes my current C development system is more than adequate?

>Since linking with CLIPPER.LIB is the main problem wouldn't it be possible to
>place the BC++ library before the CLIPPER library when linking so that the
>references are resolved in the BC++ library?  After all it is the code in BC++
>library that would be executing the code?

>Is Nantucket planning to improve its product to cater for BORLAND supporters?

>Is BORLAND planning to add MSC floating point capability?

Are you sure that Borland products are linkable AT ALL with .LIB?
I didn't think that this was possible.
-- 
Kevin Kleinfelter @ Dun and Bradstreet Software, Inc (404) 239-2347
...gatech!nanovx!msa3b!kevin
Warning: There seem to be multiple 'msa3b' nodes on Usenet, and it is
nanoVX, not nanovAx.