Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!mcnc!ecsvax!tpmsph
From: tpmsph@ecsvax.UUCP (Thomas P. Morris)
Newsgroups: comp.sys.ibm.pc,comp.lang.c
Subject: Re: Turbo C libraries
Message-ID: <3752@ecsvax.UUCP>
Date: Tue, 25-Aug-87 09:00:58 EDT
Article-I.D.: ecsvax.3752
Posted: Tue Aug 25 09:00:58 1987
Date-Received: Wed, 26-Aug-87 06:09:40 EDT
References: <351@philmds.UUCP> <1671@brspyr1.BRS.Com>
Organization: UNC Educational Computing Service
Lines: 20
Summary: missing the point
Xref: mnetor comp.sys.ibm.pc:7105 comp.lang.c:3893

> in article <351@philmds.UUCP>, corne@philmds.UUCP (corne) says:
  > 
  > I'm using the TURBO C compiler on mine AT, but my hardware was supplied 
  > with microsoft C libraries (no source code).
  > 
  > Does any one know how I can link the libraries (microsoft format) with
  > my TURBO C files.
  > 
> 
	Some of the folks who have answered this seem to have missed an 
essential point (or perhaps several :-). Sure, one ought to be able to
use the Microsoft C linker---due to MS-C's use of "undocumented" object
record types which TLINK cant handle---but there are other problems or
questions which come to mind. Are the register usage and calling conventions
for MS-C and TC the same? If not, all sorts of unexpected behavior would
result. Also, the resultant EXE file would likely    require much of BOTH
the MS-C and TC run-time "helper" routines to be linked into the image,
requiring the MSC libraries. One might be able to work around this by
writing interface routines with the same names and functions, but that
would be a major effort.  Sorry if I rained on anyone's parade.