From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sun, 7 Apr 2024 13:41:34 -0500 Subject: new repository --- devdocs/gcc~13/backwards-compatibility.html | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 devdocs/gcc~13/backwards-compatibility.html (limited to 'devdocs/gcc~13/backwards-compatibility.html') diff --git a/devdocs/gcc~13/backwards-compatibility.html b/devdocs/gcc~13/backwards-compatibility.html new file mode 100644 index 00000000..0741dcdd --- /dev/null +++ b/devdocs/gcc~13/backwards-compatibility.html @@ -0,0 +1,7 @@ +

7.12 Backwards Compatibility

Now that there is a definitive ISO standard C++, G++ has a specification to adhere to. The C++ language evolved over time, and features that used to be acceptable in previous drafts of the standard, such as the ARM [Annotated C++ Reference Manual], are no longer accepted. In order to allow compilation of C++ written to such drafts, G++ contains some backwards compatibilities. All such backwards compatibility features are liable to disappear in future versions of G++. They should be considered deprecated. See Deprecated Features.

Implicit C language
+

Old C system header files did not contain an extern "C" {…} scope to set the language. On such systems, all system header files are implicitly scoped inside a C language scope. Such headers must correctly prototype function argument types, there is no leeway for () to indicate an unspecified set of arguments.

+

+ © Free Software Foundation
Licensed under the GNU Free Documentation License, Version 1.3.
+ https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/Backwards-Compatibility.html +

+
-- cgit v1.2.3