fortify-headers/include/sys/socket.h, branch 1.1

Don't use extension in C++ code

2018-07-24T10:00:30Z

A few important notes: * __extension__ is a GNU C "alternate" keyword, not a C++ keyword.[1] * __extension__ is designed to work on "expressions"; it does work on #include_next in C mode, but it has no effect in C++ mode; the warning will still appear, if enabled, even with __extension__ preceding #include_next. This is because #include_next is not considered an expression in C++, so the compiler attaches __extension__ to the first expression of the header. All of this leads us to a build failure while building at least all Mozilla software. Moz has an alternate -isystem dir searched before /usr/include that overrides some headers, including . The first statement in each of these headers is a #pragma, and since __extension__ is looking for an expression, and #pragma is a "null" expression, we end up with the following error: dist/system_wrappers/features.h:1:9: error: '#pragma' is not allowed here Since __extension__ has no effect on #include_next in C++ mode anyway, and since it can cause breakage, this commit omits __extension__ in C++ mode. [1]: https://gcc.gnu.org/onlinedocs/gcc-6.4.0/gcc/Alternate-Keywords.html

Bump copyright year

2016-09-10T11:54:17Z

Add extension mark to include_next to silence -pedantic

2015-06-25T09:18:26Z

Signed-off-by: Steven Barth

Use namespace-safe macro, param and variable names

2015-06-03T17:55:35Z

Add LICENSE header

2015-05-13T11:15:36Z

Add fortify_fn() helper in fortify-headers.h

2015-05-13T11:05:29Z

Use typeof to in part avoid replicating function types

2015-03-14T20:37:27Z

Add artificial to aid in debugging

2015-03-14T09:38:22Z

Restore C++ support

2015-03-13T23:09:15Z

Rework fortify implementation to use extern inline

2015-03-13T11:00:46Z

Overriding functions with macros is legal in C but a lot of software is not prepared for it. Use the extern inline method to achieve the same result.