https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70476
--- Comment #15 from Jiang An <de34 at live dot cn> --- (In reply to Maciej S. Szmigiero from comment #14) > > This is not so useful in practice because most compilers don't make extern > > "C" and extern "C++" differentiate function types (implying calling > > conventions etc.). > > The standard allows different calling conventions for "C" and "C++" language > linkage and that's what matters when writing standard-compliant code - one > shouldn't write to a particular implementation (or implementations). > The problem in pratice is that most implementations are not standard-compliant here. If you rely on the standard guarantee that extern "C" and extern "C++" make function types different, you probably get compilation errors. > > > All functions and variables whose names have external linkage and all > > > function types have a language linkage. > > > > which implies that a function with internal linkage doesn't have a language > > > linkage, and thus [dcl.link]/7 doesn't apply to it. > > Nothing in the above quote says that *only* these specified have a language > linkage, just that these explicitly enumerated sure do. I think the italic style is "the thing", which should mean that the term "language linkage" is introduced and restricted here.
