** Reply to message from Martin Dalecki <[EMAIL PROTECTED]> on Thu,
28 Sep 2000 20:31:05 +0200
> Simple: The fact that G++ is constantly changing what it's generatign
> even
> between minor numbers:
>
> 1. Calling conventions.
> 2. Name mungling.
> 3. Construct semantics.
> 4. Run time support (stdio and STL).
> 5. New features here and there...
>
> and so on and so on...
Binary compatibility in C++ was NEVER an option, on any platform. The C++
standard specifically excludes any definition for the binary layout of classes
and calling conventions. Anyone who writes "modules" (e.g. DLLs, drivers,
whatever) knows that you can't have cross-module C++ calls. Everything must be
translated to C calls with a standard calling convention (typically the Pascal
calling convention on Windows and OS/2).
--
Timur Tabi - [EMAIL PROTECTED]
Interactive Silicon - http://www.interactivesi.com
When replying to a mailing-list message, please don't cc: me, because then I'll just
get two copies of the same message.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
