|
 (Click here for a personal note from Marshall Cline.) |
|
Section 38:
| 38.1 | Where can I download a free C++ compiler? |
| 38.2 | Where can I get more information on using MFC and Visual C++? |
| 38.3 | How do I display text in the status bar using MFC? |
| 38.4 | How can I decompile an executable program back into C++ source code? |
| 38.5 | Where can I get information about the C++ compiler from {Borland, IBM, Microsoft, Sun, etc.}? |
| 38.6 | What's the difference between C++ and Visual C++? |
| 38.7 | How do compilers use "over-allocation" to remember the number of elements in an allocated array? |
| 38.8 | How do compilers use an "associative array" to remember the number of elements in an allocated array? |
| 38.9 | If name mangling was standardized, could I link code compiled with compilers from different compiler vendors? |
| 38.10 | GNU C++ (g++) produces big executables for tiny programs; Why? |
| 38.11 | Is there a yacc-able C++ grammar? |
| 38.12 | What is C++ 1.2? 2.0? 2.1? 3.0? |
| 38.13 | Is it possible to convert C++ to C? |
E-mail the author
[38.9] If name mangling was standardized, could I link code compiled with compilers from different compiler vendors?
Short answer: Probably not.
In other words, some people would like to see name mangling standards incorporated into the proposed C++ ANSI standards in an attempt to avoiding having to purchase different versions of class libraries for different compiler vendors. However name mangling differences are one of the smallest differences between implementations, even on the same platform.
Here is a partial list of other differences:
- Number and type of hidden arguments to member functions.
- is this handled specially?
- where is the return-by-value pointer passed?
- Assuming a v-table is used:
- what is its contents and layout?
- where/how is the adjustment to this made for multiple and/or virtual inheritance?
- How are classes laid out, including:
- location of base classes?
- handling of virtual base classes?
- location of v-pointers, if they are used at all?
- Calling convention for functions, including:
- where are the actual parameters placed?
- in what order are the actual parameters passed?
- how are registers saved?
- where does the return value go?
- does caller or callee pop the stack after the call?
- special rules for passing or returning structs or doubles?
- special rules for saving registers when calling leaf functions?
- How is the run-time-type-identification laid out?
- How does the runtime exception handling system know which local objects need to be destructed during an exception throw?