diff options
author | Brooks Moses <bmoses@google.com> | 2013-12-11 17:46:46 -0800 |
---|---|---|
committer | Brooks Moses <bmoses@google.com> | 2013-12-23 15:50:54 -0800 |
commit | 3f637079f549956fe71a363fd82e1b66295deda2 (patch) | |
tree | fb4a09326c7092e81e9dfe937abe18e0e73aa403 /string/test-strcasecmp.c | |
parent | abc26e998f74750850cc02f9c249ee794cbdd8e8 (diff) | |
download | glibc-3f637079f549956fe71a363fd82e1b66295deda2.tar.gz glibc-3f637079f549956fe71a363fd82e1b66295deda2.tar.xz glibc-3f637079f549956fe71a363fd82e1b66295deda2.zip |
Define __CORRECT_ISO_CPP_STRING_H_PROTO correctly for Clang.
In the string/string.h and string/strings.h headers, we have a couple of macros that "tell the caller that we provide correct C++ prototypes" according to the comment; they are used to determine whether to wrap some prototypes in "extern "C++"" (and provide multiple overloads of them, and some other magic) when __cplusplus is defined. The macros are set to check for sufficiently-recent GCC versions (4.4 and later), but this is not the right check for non-GCC compilers. In particular, these macros should also be set when using Clang -- if they are not set, then Clang will be unable to correctly diagnose a number of subtle bugs that will be errors in GCC compilations. As per discussion on earlier versions of this patch, rather than restrict the fix to Clang per se, we assume that all C++ compilers that claim to fully support C++98 are using a standard-conforming C++ standard library, which seems pretty reasonable. Clang has been providing an appropriate value of __cplusplus since May 2012.
Diffstat (limited to 'string/test-strcasecmp.c')
0 files changed, 0 insertions, 0 deletions