Editing Name mangling (section)

====Standardized name mangling in C++====
It would seem that standardized name mangling in the C++ language would lead to greater interoperability between compiler implementations. However, such a standardization by itself would not suffice to guarantee C++ compiler interoperability and it might even create a false impression that interoperability is possible and safe when it isn't. Name mangling is only one of several [[application binary interface]] (ABI) details that need to be decided and observed by a C++ implementation. Other ABI aspects like [[exception handling]], [[virtual table]] layout, structure, and stack frame [[Data structure alignment|padding]] also cause differing C++ implementations to be incompatible. Further, requiring a particular form of mangling would cause issues for systems where implementation limits (e.g., length of symbols) dictate a particular mangling scheme. A standardized ''requirement'' for name mangling would also prevent an implementation where mangling was not required at all – for example, a linker that understood the C++ language.

The [[ISO/IEC 14882|C++ standard]] therefore does not attempt to standardize name mangling. On the contrary, the ''Annotated C++ Reference Manual'' (also known as ''ARM'', {{ISBN|0-201-51459-1}}, section 7.2.1c) actively encourages the use of different mangling schemes to prevent linking when other aspects of the ABI are incompatible.

Nevertheless, as detailed in the section above, on some platforms<ref>{{cite web|url=https://itanium-cxx-abi.github.io/cxx-abi/abi.html#mangling|title=Itanium C++ ABI, Section 5.1 External Names (a.k.a. Mangling)|access-date=16 May 2016}}</ref> the full C++ ABI has been standardized, including name mangling.