Subj : C++ and C libraries
To   : borland.public.cpp.borlandcpp
From : Luigi Fonti
Date : Tue Apr 27 2004 10:34 am

I have an application developed for MSDOS using Borland C++ 4.0
Now, to add network functionalities to it, I should link a TCPIP library
written just for Borland environments (wattcp).
I got libraries (for different memmory models) and sources, too.
Unhappily if I insert in my sources some calls to TCPIP functions, the
libraries are not linked, and the called fuctions remains unresolved.
I made a very small test application (3 lines of source code) with the same
result.
The problem seens to be in source types: the application sources are .cpp,
while the TCPIP library sources are .c
If I make the same application , changing the extension of the main source
file from .cpp to .c, the everyting work, and the linker succeeds resolving
all the external references. It seems BC++4.0 doesn't accept to mix object
files coming from .c and .cpp source files together.
But my real application is written in C++, and has all the source files .cpp
Is there a solution ? Is it possible in BC++4.0 to change some option and
let it link .c and .cpp files ?
Thanks in advance
Luigi Fonti

.