Topic: Compatibility between Microsoft-C and Borland-C Object modules ?
Author: prastogi@netcom.com (Parag Rastogi[Perugi] 408 996 0443)
Date: Wed, 15 Jul 92 16:21:19 GMT Raw View
How different is Microsoft-C Compild module and Borland C compiled modules.
DO they follow different conventions for generating the assembly code and the
object code. Is it possible to link object modules and libraries generated by
different compilers.
The reason I am asking this question is I am trying to use a product called
JAM (JYACC Application Manager) which is a user-interface building tool that
uses Microsoft-C. It has some C-libraries that are compatible with Microsoft C.
But I personally have a passion for Borland C/C++ products, because of its
rich environment and also the cost-effectiveness.
Before I buy this product, I want to feel sure if the above combination could
work. Also I am wondering if there is any tool in the shareware whic would
be useful for ensuring compatibility between Microsoft and Borland generated
modules if there exists any incompatibility.
Any pointers to resolve above can be very useful. I will like to post the
summary if there is significant interest.
Parag Rastogi
(916)-636-7379
--
"Of ______ course it's the murder weapon. Who would frame someone with a
fake?"
-----------------------------------------------------------------------
#include <std_disclaimers.h>
From:prastogi@netcom.com
-----------------------------------------------------------------------