Re: Using Borland C++ object files in VC++
"Jochen Kalmbach [MVP]" wrote:
Object files does not contain any dos-specific functions,
only some
mathematical algorithms are implemented there. I know
VC++ dlls can be
imported by Borland using implib, impdef etc, and this
proof of the
conversion is why i am hopeful.
This has nothing to do with dos functions or not.
If that object file was compiled under dos, for dos, it
is 16 bit code. not 32 bit code.
Hmm... 16-bit opcodes are fully compatible with 32-bit
opcodes...
The problem is not opcodes, obviously. The object file in
question contains 16-bit code, which cannot be linked with
32-bit code. Pointers have different sizes, parameters have
different sizes, prolog/epilog is different, alignment and
padding are different etc etc.. These are simply different
worlds.
A 32 bit compiler like VC6 cannot do anything with that
code, even if it could use borland object files, which it
can't.
Hmm... VC compiler always had support for OMF object
format! which is used by borland and early MS compilers!
For C functions this may work, but not for C++ binary code.
object files are compiler specific, and the contents of
the object files are not portable between compiler
versions.
This is not 100% true... if there is no dependecy to other
libs, then you can use the obj file...
Dependency to other libs is least problem here. We're
speaking about C++ binary code. Even different versions of
compiler of the same vendor won't agree on binary C++ files.
How 16-bit C++ binary (from other vendor!) can possible be
linked togeter with 32-bit binaries? Name mangling is not
compatible, objects' memory layout is not compatible, even
most benign `sizeof' statements produce different results.
They just can't work together.
Alex