Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!cs.utexas.edu!execu!sequoia!balkan!wgb
From: wgb@balkan.tnt.COM (William G. Bunton)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: MS Linker errors
Message-ID: <1990Mar29.125645.4546@balkan.TNT.COM>
Date: 29 Mar 90 12:56:45 GMT
References: <7437@hydra.gatech.EDU> <2414@dataio.Data-IO.COM>
Sender: wgb@balkan.TNT.COM (William G. Bunton)
Distribution: usa
Organization: Tools & Techniques, Inc.
Lines: 28
In-Reply-To: bright@Data-IO.COM's message of 28 Mar 90 21:43:40 GMT

>>>>> In article <2414@dataio.Data-IO.COM>, bright@Data-IO.COM (Walter Bright) writes:

> In article <7437@hydra.gatech.EDU> gb7@prism.gatech.EDU (Joe Bradley) writes:
> <I am developing an application with Zortech's C++ v2.0. I need to link
> <with a 3rd party library which was built with MS C v5.0.

> I recommend that you call the vendor of the 3rd party library and
> request that they send you a Zortech version.

About a year and a half ago, we bought Watcom C.  One of the great
features was we could set up calling conventions to be compatible with
any existing C library.  Unfortunately, that was only if you didn't
link with the Watcom library.  I called and asked about this, because
we too have to link with existing 3rd party libraries built with MSC.
The response from Watcom was 'Call the vendor of the 3rd party library
and request that they send you a Watcom version'.  Our response was to
send Watcom C back, and continue using MSC.

Walter, I own Zortech C++ v2.0.  Actually, it's now 2.06 after waiting
two months for Zortech to to upgrade me, and finally having to call
them.  But I can't use it, because we still have to link with existing
3rd party libraries built with MSC.  So I guess we'll look into buying
Intek or Guidelines C++.  Too bad, because I like Zortech.

Bill
-- 
William G. Bunton                                        wgb@balkan.tnt.com
Tools & Techniques, Inc. Austin, TX        {cs.utexas.edu,uunet}!balkan!wgb