From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Compiling libraries
Date:	29 Sep 2000 14:16:18 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	23
Message-ID:	<8r287i$6tg$1@nets3.rz.RWTH-Aachen.DE>
References:	<39D4440B DOT 7BF4FB88 AT yahoo DOT com> <8r1q2j$rhr$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <39D49275 DOT CCF6A4E9 AT yahoo DOT com>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
Mime-Version:	1.0
X-Trace:	nets3.rz.RWTH-Aachen.DE 970236978 7088 137.226.32.75 (29 Sep 2000 14:16:18 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	29 Sep 2000 14:16:18 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Juan L. Jiménez Bascones <jljbascones AT yahoo DOT com> wrote:
>   And if the code is generated by different compilers (MS D. Studio 6.0,
> DJGPP) but under the same platform?

But the platform _is_ not the same, for these two compilers. Not
unless you count RSXNTDJ as an integral part of DJGPP that doesn't
need to be mentioned in such a sentence, that is.

'Platform' is more than just the CPU. DJGPP is 32bit DOS, MSVC++ is
32bit Windows, exclusively. These are different platforms.

There are cases where code is indeed platform-independent, as long as
the CPU is the same, but such code hard to create.  It imposes
limitations like what you have in .dxe files for DJGPP: no calling of
library functions, neither explicitly nor behind the scenes.

And even then the 'application binary interface' (aka the 'call
convention' ) may still be wildly different, or the object file
formats may be incompatible.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -